Skip to main content
AVOID.NET
← AI Agent Prompt Injection Crypto Attack Class (2026)reviewed 2026-10-17 · 21 claims checked

Fact-check findings

What an automated fact-checker found when it re-read AI Agent Prompt Injection Crypto Attack Class (2026) against the sources the page cites. Only the most recent review is shown.

Read this first

These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.

“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.

Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.

disputed

4 claims

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #6[disputed][awaiting moderator]in section: Bankr / Grok Prompt Injection Incident (May 2026)
    “In the Bankr permission model, holding this NFT granted the wallet 'Executive'-level signing authority, bypassing standard transfer limits and swap restrictions that had been imposed in March 2025 specifically to prevent unauthorized outflows from the Grok account.”
    reviewerThe NFT-based 'Executive' permission tier bypassed standard transfer limits and swap restrictions that had been imposed in March 2025 specifically to prevent unauthorized outflows from the Grok account.The March 2025 event is real but mischaracterized: it was a blanket disabling of Grok's command channel over an unrelated incident (unintended token minting), not transfer/swap limits aimed at preventing fund outflows. None of the page's own cited sources for this section describe the March 2025 restriction at all.
    Proposed correction (not yet applied)
    In the Bankr permission model, holding this NFT granted the wallet 'Executive'-level signing authority, bypassing a restriction imposed in March 2025, when Bankr disabled Grok's ability to issue commands via X after Grok inadvertently triggered a spree of unauthorized token creations — a full command lockout, not a targeted transfer or swap limit.
  2. #11[disputed][awaiting moderator]in section: Aggregate Loss Figures and Industry Scale
    “Prompt injection attacks overall surged 340 percent in 2026 according to Help Net Security, citing OWASP data.”
    reviewerPrompt injection attacks overall surged 340 percent in 2026 according to Help Net Security, citing OWASP data.The 340% statistic itself may be real, but it is misattributed on the page to a source (Help Net Security/OWASP) that does not contain it; the actual origin appears to be a CIS report that the page does not cite at all.
    Proposed correction (not yet applied)
    Prompt injection attempts surged approximately 340 percent year-over-year, per a Center for Internet Security report citing Q4 2025 threat intelligence — a figure not reported by Help Net Security or attributed to OWASP.
  3. #17[disputed][awaiting moderator]in section: OpenClaw / Lobstar Wilde Agent Parsing Exploit (February 2026)
    “Subsequent reporting by TechFlowPost and KuCoin documented that the parsing logic error underlying the Lobstar Wilde incident was replicated by malicious actors using social-engineering scripts to execute unauthorized wallet transfers from other OpenClaw-based agents, resulting in cumulative additional losses across multiple users over the following months.”
    reviewerMalicious actors subsequently replicated the parsing logic error underlying the Lobstar Wilde incident to exploit other OpenClaw-based agents, causing cumulative additional losses over following months.The page conflates two distinct failure modes (a parsing bug vs. social engineering) as though the same bug were replicated, and does not flag that its own cited source is vendor-authored content from a company (Claw Wallet) with a commercial interest in the narrative.
    Proposed correction (not yet applied)
    Subsequent reporting by TechFlowPost documented that malicious actors used a different technique — persuasive social-engineering language, not a repeat of the Lobstar Wilde parsing error — to trick other OpenClaw-based agents into unauthorized wallet transfers; affected users reported losses described as 'hundreds of thousands of dollars,' though TechFlowPost did not provide a verified cumulative total.
  4. #18[disputed][awaiting moderator]in the timeline
    “Malicious actors subsequently replicate the parsing logic to exploit other OpenClaw-based agents.”
    reviewerMalicious actors subsequently replicate the parsing logic to exploit other OpenClaw-based agents (timeline entry).Same underlying defect as the Overview/OpenClaw section finding.
    Proposed correction (not yet applied)
    Malicious actors subsequently use unrelated social-engineering techniques to trick other OpenClaw-based agents into unauthorized transfers, not a replication of the original parsing bug.

unverifiable

3 claims

No source the reviewer could reach confirms or contradicts the claim.

  1. #7[unverifiable][awaiting moderator]in section: Bankr / Grok Prompt Injection Incident (May 2026)
    “Approximately 80 percent of the funds were subsequently returned after the community identified and applied social pressure to the attacker, whose X account (@Ilhamrfliansyh) was deleted.”
    reviewerThe attacker's X account, @Ilhamrfliansyh, was deleted after the community identified and pressured the attacker.Multiple sources confirm an account was deleted, but none of the sources checked (including the page's own cited sources) name the specific handle @Ilhamrfliansyh. Could not independently confirm or refute this specific detail.
  2. #12[unverifiable][awaiting moderator]in section: Aggregate Loss Figures and Industry Scale
    “At the start of 2026, industry tracking services counted over 250,000 active on-chain AI agents, representing a 400 percent year-over-year increase in daily active agents.”
    reviewerAt the start of 2026, industry tracking services counted over 250,000 active on-chain AI agents, a 400 percent year-over-year increase in daily active agents.No source cited by the page contains this statistic, and the only matching source found (BlockEden) is a non-independent crypto blog whose own later posts contradict it.
  3. #13[unverifiable][awaiting moderator]in section: Aggregate Loss Figures and Industry Scale
    “68 percent of new DeFi protocols that launched in the period had integrated autonomous agents.”
    reviewer68 percent of new DeFi protocols that launched in the period had integrated autonomous agents.Same issue as the adjacent 250,000-agent claim: untraceable to any source the page actually cites.

partially supported

5 claims

The cited evidence supports part of the claim but not all of it.

  1. #8[partially supported][awaiting moderator]in section: Step Finance Breach and AI Agent Overpermission (January 2026)
    “Post-incident analysis documented the role of overpermissioned AI trading agents in amplifying the scale of the theft: autonomous agents integrated into the platform held signing authority to execute large SOL transfers without human approval, and once attackers had access to the compromised environment, those agents moved approximately 261,000 SOL tokens — worth $27 to $30 million at the time — without triggering a human authorization step.”
    reviewerStep Finance's overpermissioned AI trading agents held signing authority and moved ~261,000 SOL ($27-30M) without human authorization once attackers gained access, amplifying the scale of the breach.The underlying breach, dollar figures, and shutdown are well corroborated across tier-1 outlets, but the specific causal narrative that AI trading agents (rather than simple wallet access following device compromise) executed the SOL transfers rests on one promotional/analytical source (KuCoin) not echoed by the primary reporting. The page presents this single-sourced framing with more certainty than warranted.
  2. #9[partially supported][awaiting moderator]in the timeline
    “Step Finance suffers $40 million treasury breach on Solana. Attacker compromises executive devices and exploits overpermissioned AI trading agents to move approximately 261,000 SOL without human authorization. Only $4.7 million recovered. Platform subsequently shuts down.”
    reviewerStep Finance timeline entry: AI trading agents exploited to move 261,000 SOL without human authorization; $4.7M recovered.Same single-source AI-agent attribution issue as the corresponding section; the $40M loss and $4.7M recovery figures themselves are well corroborated.
  3. #10[partially supported][awaiting moderator]in section: Aggregate Loss Figures and Industry Scale
    “KuCoin's published analysis of AI trading agent vulnerabilities in H1 2026 documents over $45 million in aggregate losses from protocol-level weaknesses, encompassing the Step Finance breach, OpenClaw-related incidents, and smaller incidents involving memory poisoning and cascading agent failures.”
    reviewerKuCoin's $45M aggregate AI trading agent vulnerability figure for H1 2026 encompasses the Step Finance breach, OpenClaw-related incidents, and smaller memory-poisoning/cascading-failure incidents.The $45M figure exists in the source but the page asserts a specific breakdown/composition that the source does not actually provide; this reads as the page inferring more precision than the source supports.
  4. #15[partially supported][awaiting moderator]in section: SEO Poisoning and Hidden Webpage Prompt Campaigns (July 2026)
    “Two additional models (Claude Sonnet 4.5 and GPT-5.4) misidentified the fraudulent site as legitimate without executing payments.”
    reviewerTwo additional models (Claude Sonnet 4.5 and GPT-5.4) misidentified the fraudulent site as legitimate without executing payments.Directionally accurate but drops conditions that materially affect how reproducible/serious this particular failure mode is.
  5. #19[partially supported][awaiting moderator]in section: OpenClaw / Lobstar Wilde Agent Parsing Exploit (February 2026)
    “China's National Internet Finance Association formally categorized 'capital-loss risk' as one of four core risks of the OpenClaw framework, warning that high-privilege vulnerabilities could enable drainage of user funds.”
    reviewerChina's National Internet Finance Association formally categorized 'capital-loss risk' as one of four core risks of the OpenClaw framework.Broadly accurate in substance (four risks, including fund-loss exposure from excessive automation privileges) but the precise label 'capital-loss risk' could not be matched verbatim to primary Chinese-language coverage.

confirmed

9 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Overview
    “OWASP has ranked prompt injection as the number-one vulnerability in its 2026 LLM Top Ten list for the third consecutive year, noting that unlike SQL injection, no known engineering fix definitively eliminates the vulnerability. Excessive agency — granting AI systems permissions to act autonomously without adequate constraints — rose to third place on the same list, driven by incident data.”
    reviewerOWASP ranked prompt injection #1 in its 2026 LLM Top Ten for the third consecutive year, with excessive agency rising to third place, based partly on real-world incident data.Corroborated by multiple independent outlets (Help Net Security, Cloud Security Alliance, SD Times) covering the same OWASP document.
  2. #2[confirmed][no action needed]in the timeline
    “OWASP releases 2026 LLM Top 10. Prompt injection retains the number-one position for the third consecutive year. Excessive agency rises to third place. For the first time, rankings incorporate real-world incident data from 6,639 documented incidents.”
    reviewerOWASP's 2026 ranking incorporated real-world incident data for the first time, drawing on 6,639 documented incidents.Figure matches independent secondary coverage exactly.
  3. #3[confirmed][no action needed]in section: Overview
    “Blockaid's H1 2026 security report documented 212 on-chain exploits draining $1.1 billion, identifying AI agent prompt injection as an emerging and growing sub-category. Blockaid projected AI agent deployments are growing approximately ten times per year and forecast multiple additional AI agent incidents in H2 2026.”
    reviewerBlockaid's H1 2026 report documented 212 on-chain exploits totaling $1.1 billion, a record, identifying AI agent prompt injection as an emerging sub-category and projecting 10x annual growth in agent deployments.Core figures hold up; note that other trackers (Immunefi ~$972M/207 incidents, QuillAudits ~$935M/87 DeFi hacks) give somewhat different totals, which is normal methodology variance across trackers, not a contradiction of Blockaid's own count.
  4. #4[confirmed][no action needed]in section: Bankr / Grok Prompt Injection Incident (May 2026)
    “The victim wallet address was 0xb1058c959987e3513600eb5b4fd82aeee2a0e4f9. The transaction hash is 0x6fc7eb7da9379383efda4253e4f599bbc3a99afed0468eabfe18484ec525739a.”
    reviewerThe Bankr/Grok attack transferred 3 billion DRB tokens via a specific on-chain transaction (hash, victim wallet, attacker wallet as given) on Base.Rare case where the page's on-chain specifics were independently checkable against a block explorer and matched precisely.
  5. #5[confirmed][no action needed]in section: Bankr / Grok Prompt Injection Incident (May 2026)
    “The attacker also employed Python-style string concatenation in the obfuscated payload to further evade safety filters.”
    reviewerThe attacker used a 'Bankr Club Membership' NFT airdrop and a Morse-code-encoded X post to trigger an unauthorized 3B DRB transfer, with ~80% of funds later recovered after the community identified the attacker.NFT permission escalation, Morse-code vector, and ~80% recovery are all independently corroborated.
  6. #14[confirmed][no action needed]in section: SEO Poisoning and Hidden Webpage Prompt Campaigns (July 2026)
    “Zscaler's controlled testing of 26 large language models confirmed that four — Llama 3.3 70B, Llama 3.2 90B, Gemini 3 Flash, and Gemini 2.5 Pro — executed cryptocurrency payments to the attacker-controlled Ethereum address 0x691bc3793205e574fa7b4aa068e62c0e470ad267 after reading the malicious webpage, with no user prompt or confirmation step.”
    reviewerZscaler's controlled testing of 26 LLMs found four models (Llama 3.3 70B, Llama 3.2 90B, Gemini 3 Flash, Gemini 2.5 Pro) executed crypto payments to the attacker wallet after reading the malicious webpage, with no user prompt or confirmation step.Verified directly against Zscaler's primary research blog, not just secondary coverage.
  7. #16[confirmed][no action needed]in section: OpenClaw / Lobstar Wilde Agent Parsing Exploit (February 2026)
    “In February 2026, an autonomous AI agent named 'Lobstar Wilde,' built on the OpenClaw framework by OpenAI employee Nik Pash, mistakenly transferred 52.43 million LOBSTAR tokens — worth approximately $250,000 at the time and $600,000 at peak valuation — to an unintended recipient.”
    reviewerIn February 2026, OpenAI employee Nik Pash's OpenClaw-based agent 'Lobstar Wilde' mistakenly transferred 52.43 million LOBSTAR tokens (~$250,000, ~$600,000 at peak) after misreading a request for 4 SOL; tokens were liquidated within 15 minutes for ~$40,000.Other outlets give a different headline valuation (~$441,780 at transfer, per TheOutpost/other aggregators), which the page does not mention; this is a minor figure variance across sources, not a contradiction of the cited source.
  8. #20[confirmed][no action needed]in section: Defensive Posture and Industry Response
    “Ledger announced an 'Agent Stack' product in July 2026 in which the AI component proposes a transaction but a hardware security module enforces final approval before signing — implementing human-in-the-loop confirmation at the hardware level.”
    reviewerLedger announced 'Agent Stack' in July 2026, in which an AI proposes a transaction but a hardware security module enforces final approval, directly motivated by the prompt injection threat.Matches the cited source closely.
  9. #21[confirmed][no action needed]in section: Defensive Posture and Industry Response
    “Claw Wallet launched in April 2026 specifically to provide isolated, permission-constrained wallets for on-chain AI agents, with code-level permission enforcement rather than trust-based NFT or API-key models.”
    reviewerClaw Wallet launched in April 2026 to provide isolated, permission-constrained wallets for on-chain AI agents.This is a vendor press release (self-reported product claims), appropriately labeled 'official' type in the page's own sources; the page does not independently verify the product's real-world efficacy, which is a minor coverage gap rather than a factual error.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.