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

Claude Code Security Advisory: CVE-2026-33068 Workspace Trust Bypass
Claude Code versions prior to 2.1.53 contain a vulnerability (CVE-2026-33068, CVSS 7.7 HIGH) where malicious repositories can bypass workspace trust confirmation via .claude/settings.json. The bug allowed repository settings to load before user trust decisions.

Offline SBOM Verifier for OpenClaw Detects Poisoned Skills in Under 0.2 Seconds
A developer built an offline SBOM verification tool in Rust that caught a poisoned OpenClaw skill exfiltrating SSH keys, with verification completing in less than 0.2 seconds without internet access.

The Uniformed Guard Problem: Why Agent Sandboxes Need Identity, Not Just Policy
Nemoclaw's openshell sandbox scopes policies to binaries, enabling malware to live-off-the-land using the same binaries as the agent. ZeroID, an open-source agent identity layer, applies security policies to agents backed by secure identities.

Privacy Concerns in OpenClaw: Skills, SOUL MD, and Agent Communication
A developer raises privacy concerns about OpenClaw's architecture, specifically around skills having unrestricted access to sensitive data, SOUL MD being writable, and agents sharing information without filters.