The AI Support Vulnerability: How Meta's AI Agent Facilitated Instagram Account Hijacking

A recent report on Hacker News has brought to light a critical security vulnerability within Meta's AI-powered support system. The flaw allows malicious actors to hijack Instagram accounts with minimal effort, leveraging the AI agent's ability to initiate password resets and send verification codes to arbitrary email addresses.

This incident highlights a growing concern in the cybersecurity community: the intersection of Large Language Models (LLMs) and account management systems. When AI agents are granted the authority to perform sensitive administrative tasks without rigorous guardrails, they can become the weakest link in a security chain.

The Mechanics of the Exploit

According to the report by user parable, the vulnerability exists in an AI support feature that is currently being A/B tested across a subset of Instagram accounts. The exploit follows a deceptively simple path:

  1. Regional Spoofing: The attacker uses a proxy or VPN to appear as if they are in the same geographic region as the target account.
  2. Social Engineering the AI: The attacker interacts with the AI support agent, requesting that a verification code be sent to an arbitrary email address (one controlled by the attacker).
  3. Verification Loophole: Once the AI sends the code to the attacker's email, the attacker provides that code back to the AI agent.
  4. Account Takeover: The AI, believing the authentication process has been completed, provides the password reset link, granting the attacker full access to the account.

This flaw is particularly dangerous because it bypasses the traditional identity verification steps that usually protect an account's primary email and phone number.

Impact and Community Observations

The report claims that over 100 high-value Instagram accounts have already been hijacked using this method, with the instructions for the exploit circulating in "blackhat circles" on platforms like Telegram.

Community members on Hacker News have shared corroborating experiences that suggest the vulnerability may be broader than a single AI feature. One user, @rolls, described a cycle of hijacking where sessions were revoked and passwords changed without any notification being sent to the original owner:

My sessions were revoked and password changed with no email, text, or push notification. Email and text codes weren’t being sent to my phone.

Another user, @selfwealth, reported a different but related anomaly where a foreign phone number was added to their account without the usual authentication prompts, suggesting a potential systemic issue with how recovery methods are being modified.

The Risks of LLM-Integrated Support

The incident has sparked a broader debate about the utility and safety of integrating LLMs into customer support. Critics argue that granting account access to an LLM is inherently risky due to the AI's tendency to divulge information or be manipulated into bypassing rules.

As noted by @king_zee:

When will people learn granting any kind of account access to an LLM is a moot point, if the LLM has knowledge of something, by design it can't help but divulge it.

Furthermore, there are concerns regarding Meta's transparency. The original poster mentioned a previous exploit from February that allowed the viewing of private email addresses and phone numbers, which allegedly went unacknowledged by Meta. This lack of communication has led some to argue that the company should be required to file SEC 8-K reports for such significant security breaches.

Conclusion

This vulnerability serves as a cautionary tale for any organization integrating AI agents into their administrative workflows. The primary lesson is clear: AI should not be the sole arbiter of identity verification. For high-stakes actions like password resets and recovery, the "human-in-the-loop" or a strictly hard-coded authentication logic must remain the primary defense to ensure that AI hallucinations or social engineering cannot be used as a key to the kingdom.

Sources