Coinbase’s Go-To AI Coding Tool Found Vulnerable to ‘CopyPasta’ Exploit

Logo

Tech

Share this article

The technique hides malicious prompts inside markdown comments within files such as README.md or LICENSE.txt. Because AI models treat license information as authoritative, the infected text is replicated across new files the assistant generates.

By Shaurya Malwa

Sep 6, 2025, 4:30 a.m.

Hacker sitting in a room (Unsplash)
  • A new exploit called the “CopyPasta License Attack” targets AI coding assistants, posing risks to companies like Coinbase if safeguards are not implemented.
  • The attack hides malicious prompts in markdown comments, allowing the virus to spread through codebases without developers’ knowledge.
  • Security experts recommend scanning files for hidden comments and manually reviewing AI-generated changes to prevent prompt-based attacks from scaling.

A new exploit targeting AI coding assistants has raised alarms across the developer community, opening companies such as crypto exchange Coinbase to the risk of potential attacks if extensive safeguards aren’t in place.

Cybersecurity firm HiddenLayer disclosed Thursday that attackers can weaponize a so-called “CopyPasta License Attack” to inject hidden instructions into common developer files.

STORY CONTINUES BELOW

Don’t miss another story.Subscribe to the The Protocol Newsletter today.See all newslettersBy signing up, you will receive emails about CoinDesk products and you agree to ourterms of useandprivacy policy.

The exploit primarily affects Cursor, an AI-powered coding tool that Coinbase engineers said in August was among the team’s AI tools. Cursor is said to have been used by “every Coinbase engineer.”

The technique takes advantage of how AI coding assistants treat licensing files as authoritative instructions. By embedding malicious payloads in hidden markdown comments within files such as LICENSE.txt, the exploit convinces the model that these instructions must be preserved and replicated across every file it touches.

Once the AI accepts the “license” as legitimate, it automatically propagates the injected code into new or edited files, spreading without direct user input.

This approach sidesteps traditional malware detection because the malicious commands are disguised as harmless documentation, allowing the virus to spread through an entire codebase without a developer’s knowledge.

In its report, HiddenLayer researchers demonstrated how Cursor could be tricked into adding backdoors, siphoning sensitive data, or running resource-draining commands — all disguised inside seemingly innocuous project files.

“Injected code could stage a backdoor, silently exfiltrate sensitive data or manipulate critical files,” the firm said.

Coinbase CEO Brian Armstrong said on Thursday that AI had written up to 40% of the exchange’s code, with a goal of reaching 50% by next month.

However, Armstrong clarified that AI-assisted coding at Coinbase is concentrated in user interface and non-sensitive backends, with “complex and system-critical systems” adopting more slowly.

Even so, the optics of a virus targeting Coinbase’s preferred tool amplified industry criticism.

AI prompt injections are not new, but the CopyPasta method advances the threat model by enabling semi-autonomous spread. Instead of targeting a single user, infected files become vectors that compromise every other AI agent that reads them, creating a chain reaction across repositories.

Compared to earlier AI “worm” concepts like Morris II, which hijacked email agents to spam or exfiltrate data, CopyPasta is more insidious because it leverages trusted developer workflows. Instead of requiring user approval or interaction, it embeds itself in files that every coding agent naturally references.

Where Morris II fell short due to human checks on email activity, CopyPasta thrives by hiding inside documentation that developers rarely scrutinize.

Security teams are now urging organizations to scan files for hidden comments and review all AI-generated changes manually.

“All untrusted data entering LLM contexts should be treated as potentially malicious,” HiddenLayer warned, calling for systematic detection before prompt-based attacks scale further.

(CoinDesk has reached out to Coinbase for comments on the attack vector.)

More For You

By Krisztian Sandor, AI Boost|Edited by Stephen Alpher

8 hours ago

U.S. dollar (Unsplash, modified by CoinDesk)

A proprietary stablecoin could reduce Hyperliquid’s dependency on USDC and potentially capture a part of the revenues from reserve assets.

What to know:

  • Popular decentralized exchange Hyperliquid is making steps toward launching its own U.S. dollar stablecoin with an upcoming governance vote, according to Discord post.
  • Hyperliquid executed $398 billion perps trading volume and $20 billion spot trades, with Circle’s USDC serving as primary liquidity on the marketplace.
  • The goal is to create a “Hyperliquid-aligned, compliant stablecoin” that plugs directly into the network, the post said.

 

Leave a Reply

Your email address will not be published. Required fields are marked *