AI-written npm package @kodane/patch-manager drained Solana wallets after 1,500+ downloads
npm package @kodane/patch-manager
On 28 July 2025 an npm package called @kodane/patch-manager, posing as a license-validation and registry cache tool for Node.js, was published with a hidden wallet drainer in its install script. Once installed it looked for crypto wallets on Windows, macOS and Linux and sent the funds to a Solana address, leaving just enough for fees. It was downloaded more than 1,500 times before npm flagged it on 30 July; Safety, which found it, said the code appears to be largely AI-generated. No total loss was published.
Why this severity: Many people exposed.
AI involvement
AI-built malware. Safety's researchers say the code appears largely AI-generated, citing emojis, heavy comments and logging they link to Anthropic's Claude; this is an inference from code style.
Check that a package, extension or app is the real one before installing it, even when an AI assistant suggested it.
- Started
- Jul 28, 2025
- Closed
- Jul 30, 2025
- Chains
- Solana
- Method
- Supply-chain stealers
Indicators · never visit or send to these
- sweeper-monitor-production.up.railway[.]app
- sweeper-monitor.railway[.]app
- B2XwbrGSXs3LAAcqFqKqGUug5TFA1Bug2NNGH3F3mWNK
What to do now
- Remove the package, then from a clean device move what is left to new wallets with new seed phrases.
- Reinstall the system if you cannot be sure the installer's leftover files are gone.
Stay safe
Am I affected?
If @kodane/patch-manager (any version) was installed on a machine or in a project between 28 and 30 July 2025, assume any wallet on that machine was found and drained.
What to do now
- Remove the package, then from a clean device move what is left to new wallets with new seed phrases.
- Reinstall the system if you cannot be sure the installer's leftover files are gone.
How to avoid this
- Read install scripts (postinstall) before adding unknown packages, and prefer well-known, long-lived ones.
- Never keep hot wallets on a development machine.
- Use a package scanner that flags new or suspicious packages before install.
Timeline 4
The Register reported more than 1,500 downloads and the signs of AI-written code.
SourceSafety published its analysis, including the attacker's Solana address and an open command server.
Sourcenpm marked the package as malicious.
SourceThe package was first published to npm; 19 versions followed over two days.
Source
News & write-ups ›2
How this method works
A popular code package or app update is hijacked to steal wallet keys or swap addresses, hitting everyone who installs it. Read about supply-chain stealers →
Follow new drains and updates in your feed reader or Telegram RSS bot.