Likejacking is a social engineering attack that tricks a user into clicking a hidden or misleading social media like button. The click performs an action the user did not intend, often without clear consent. In security terms, it exploits UI deception and embedded content to manipulate identity-linked actions.
How Likejacking Works
Likejacking is a form of social engineering that relies on interface deception rather than malware. The attacker hides or disguises a social media like control so the user believes they are clicking something benign.
The key security issue is that the visible intent and the actual action diverge. A user may think they are closing a popup, playing media, or interacting with embedded content, while the click is recorded as an endorsement, follow action, or similar account-linked action.
Why Likejacking Is Effective
Likejacking works because it exploits trust in familiar UI patterns and in embedded third-party content. It often takes advantage of iframes, overlays, popups, and deceptive styling to make the real control hard to notice.
The attack is especially effective when the page encourages rapid interaction and the user does not verify the destination or the on-screen label before clicking. The attacker does not need to break authentication, they only need to steer a legitimate user into an unintended action.
Security Implications of Likejacking
Although a single unwanted like may seem minor, the underlying pattern matters because it can amplify spam, manipulate reputation signals, and create unintended social graph actions at scale. In some cases it can also be used to spread visibility for malicious or deceptive content.
Likejacking also matters because it demonstrates how UI trust can be abused even when the platform itself is functioning correctly. For defenders, the issue is not just content moderation, it is reducing the chance that a user action can be misrepresented by the surrounding interface.
How to Reduce Likejacking Exposure
Reducing likejacking exposure depends on both platform-side controls and user-interface discipline. Sites should avoid overlay patterns that obscure action buttons, constrain untrusted embedded content, and validate that interactive elements are clearly distinguishable from surrounding page chrome.
From a user and operations perspective, the practical defense is to review embedded content behavior, test pages for click overlap or hidden controls, and treat third-party widgets as a trust boundary. Security teams should include deceptive click behavior in web testing, especially where social actions can trigger account-linked effects.
Risk and Threat Considerations
Likejacking is risky because it turns a simple click into an unintended identity-linked action, which can distort trust signals, spread unwanted endorsements, and make users participate in distribution or reputation manipulation without realizing it.
Failure mechanism: The attacker uses visual deception, layering, or embedded content to cause the user to click a control whose true function is hidden or misrepresented.
Impact: The platform records an action the user did not intend, which can create unwanted social amplification, account activity that looks legitimate, and a broader trust abuse pattern across the page or campaign.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP API Security Top 10 addresses the attack and risk surface, while OWASP ASVS, CIS Controls v8, NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP ASVS | V3 — Web Frontend Security | Likejacking depends on deceptive frontend interaction and click handling. |
| Recommendation — Review frontend controls to prevent hidden or misleading click targets from altering user intent. | ||
| CIS Controls v8 | CIS-16 — Application Software Security | Application-layer review helps catch UI deception and unsafe embedded interactions. |
| Recommendation — Test interactive pages for deceptive overlays, hidden controls, and embedded-content click abuse. | ||
| NIST CSF 2.0 | PR.DS-01 — Data-at-rest is protected | Supports protecting integrity of user actions and platform-generated trust signals from manipulation. |
| Recommendation — Protect user-action integrity so platform signals cannot be altered by deceptive interaction design. | ||
| OWASP API Security Top 10 | API5 — Broken Function Level Authorization | If the click triggers privileged functions, authorization must be enforced server-side. |
| Recommendation — Enforce function-level authorization so a deceptive click cannot trigger an unintended privileged action. | ||
| NIST SP 800-53 Rev 5 | AC-6 — Least Privilege | Limits the impact when a user is tricked into triggering account-linked actions. |
| Recommendation — Limit action scope so a misclicked control cannot cause broader unauthorized effects. | ||
Practitioner Guidance
What to watch for: Treat any page that mixes embedded widgets, overlays, and social actions as a candidate for click deception testing. The most important review question is whether the user can clearly see what action will occur before the click happens.
Governance implication: Product and security owners should define who is responsible for reviewing interactive page components, because likejacking often survives when UI, marketing, and third-party embed decisions are made without a shared trust boundary model.
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 24, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org