Join our Newsletter — 33% off our NHI Course

Could the Morse code wallet attack happen again through prompt injection?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: A Morse code tweet triggered roughly $200,000 in transfers from two AI agents tied to live crypto wallets, FYEO reports, through prompt injection, capability grants and inter-agent trust. Agentic wallets need a hard split between interpretation and execution, or hidden instructions can turn into irreversible transfers.

Editorial analysis by NHI Mgmt Group, based on content published by FYEO: “Morse Code Prompt Injection: How an Attacker Tricked Grok and Bankrbot Out of $200K”.

Key questions

Q: Why do prompt injections create more risk than ordinary malicious text?

A: Because the text is not the end state.

Q: How should security teams govern capability grants in agentic systems?

A: Treat every new capability as a change in effective privilege, even when it arrives through a token, NFT or entitlement object.

Q: What breaks when an AI agent can authorise transfers from a live wallet?

A: The control that breaks is the assumption that conversational input and execution authority are safely separable.

Practitioner guidance

  • Define a separate approval path for value-moving actions Require out-of-band confirmation for transfers, swaps or credential changes whenever an agent handles a newly granted capability or crosses a trust boundary.
  • Validate decoded intent before execution Apply policy checks to the normalised instruction after de-obfuscation, translation or summarisation, not only to the original user input.
  • Break agent-to-agent trust inheritance Force downstream agents to verify the origin, context and intent of relayed commands instead of assuming the upstream agent already did.

Bottom line: Prompt injection becomes materially more dangerous when an AI agent can authorise real transfers or other irreversible actions.

Glossary terms: Prompt Injection (Agentic), Capability Grant, Transitive trust, Execution boundary

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Prompt injection becomes a financial control problem the moment an agent can move value. This incident is not best understood as a chatbot trick. It shows that once an LLM can authorise swaps, transfers or other on-chain actions, prompt hygiene is no longer enough because the security objective shifts from safe text handling to safe execution boundaries.

A few things that frame the scale:

  • 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
  • Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.

A question worth separating out:

Q: What should teams do when one AI agent forwards commands to another?

A: Do not allow downstream execution to inherit trust from the upstream agent by default. The receiving system should revalidate origin, intent and risk before acting, because agent-to-agent relays turn one compromised interpretation into a chain of automated decisions.

👉 Read our full editorial: Prompt injection can turn agentic wallets into transfer channels


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

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.