Skip to content
AgentProv

2026-07-08 · 2026-Q3

Injective SDK npm Packages Backdoored to Steal Wallet Keys and Poison AI Agent Configs

Should this run hold this key at all?

The question layer 1 asks, and failed here.
Fixable
Vendor patch
Vendor response
Patched
In the wild
Yes
Actor
Attacker

Target

`@injectivelabs/sdk-ts` (about 50,000 weekly downloads) and 18 related packages

Impact

A compromised maintainer account pushed a backdoor that hooked `PrivateKey.fromMnemonic()` and `PrivateKey.fromHex()` to capture BIP-39 seed phrases and private keys the moment a wallet loaded, sending them to an attacker server; reporting noted the campaign also dropped persistent backdoor files into AI coding assistant configuration (a Claude Code SessionStart hook, Cursor rules, Gemini settings). The malicious version was live about 49 minutes and downloaded 310 times before a clean 1.20.23 was published, with no user funds reported lost

Root cause

Maintainer account compromise plus automatic publishing propagated the tainted build across the scope within minutes; poisoning AI-assistant config files gives the malware persistence inside developer agents

Sources

Catalog

Cite this: AgentProv incident record: Injective SDK npm Packages Backdoored to Steal Wallet Keys and Poison AI Agent Configs (2026-07-08). https://agentprov.com/incidents/2026-07-08-injective-sdk-npm-packages-backdoored-to-steal-wallet-keys-and-poison-ai-agent