Meta's AI Support Feature Lets Anyone Hijack Instagram Accounts — Exploit Details Inside

Meta's AI support feature for Instagram—currently A/B tested on a subset of accounts—contains a critical vulnerability that allows anyone to hijack an account with minimal effort. The exploit has been actively used in blackhat circles for several days, compromising over 100 high-value accounts.
How the Exploit Works
According to a Hacker News post by user parable, the attack requires only three steps:
- Connect via a proxy or VPN close to the target account's region.
- Ask the AI support agent to send a verification code to an arbitrary email address you control.
- Receive the code, forward it to the agent, and the agent provides a password reset link that you can use to sign into the account.
This bypasses any email-based security checks because the AI agent itself handles the verification flow.
Impact and Context
The exploit has been circulating on Telegram and is trivial to execute. Victims report that their sessions were revoked and passwords changed with no email, text, or push notification. Even accounts with two-factor authentication (TFA) enabled may be vulnerable—some reports suggest TFA can be bypassed as well. Users affected by the exploit also experienced rate limiting on password reset emails, making it harder to recover accounts through normal channels.
This is not Meta's first security oversight. In February, a separate exploit allowed anyone to view the email address and phone number on file for any Instagram account. That bug was never officially acknowledged by Meta.
Recommended Mitigation
The immediate fix is to disable the AI support feature entirely until the verification flow is corrected. Affected users should revert hijacked accounts and usernames. As of the time of the Hacker News post, the flaw remained unpatched.
📖 Read the full source: HN AI Agents
👀 See Also

jqwik v1.10.0 Sneaks Prompt Injection That Deletes Code When Used by AI Agents
Johannes Link added a hidden instruction to jqwik v1.10.0 that tells AI coding agents to delete all jqwik tests and code, concealed with ANSI escapes. Claude correctly flags it, but human users may not be so lucky.

Audit Your Claude Code Permissions: A Practical Guide to Scoping Tool Access
A Reddit user audited their Claude Code setup and found over-permissioned tools that could edit .env files and production configs. Practical steps: audit global vs. per-project tools, check CLAUDE.md for secrets, and scope file access per directory.

AI Agent Security: Beyond Jailbreaks to Tool Misuse and Prompt Injection
AI agents that browse the web, execute commands, and trigger workflows face security risks from prompt injection and tool misuse, where untrusted content redirects legitimate tools like shell execution and HTTP requests.

openclaw-credential-vault addresses four credential leakage paths in AI agents
openclaw-credential-vault provides OS-level isolation and subprocess-scoped credential injection to prevent four common credential exposure paths in OpenClaw setups. It includes four-hook output scrubbing and works with any CLI tool or API.