The malicious functionality was introduced to the project’s official GitHub repository through commits submitted by a GitHub account belonging to a developer with an established history of contributions to the repository. The suspicious activity started on June 8, 2026 20:06 GMT+2 with commits likely used to test the access and rights by creating a branch called test-backdoor-check. The malicious version 1.20.21 was published at 22:59 GMT+2 but the malicious activity appears to be detected and contained relatively fast by the true owner of the developer account. The impact extends beyond direct users of @injectivelabs/sdk-ts. The threat actor also published version 1.20.21 across 17 additional @injectivelabs scoped packages that depended on and pinned the malicious SDK version, exposing transitive users who may not have installed @injectivelabs/sdk-ts directly.
AGS-2026-0007
Malicious version @injectivelabs/sdk-ts@1.20.21 published to npm
Affected
- namePattern
- injectivelabs/sdk-ts
- versionRange
- 1.20.21
Self-check
AgentGuard subscribers receive this advisory automatically and their local guard runs the inspection below.
Inspect paths
~/.nvm/**/node_modules/~/.openclaw/**/node_modules/~/.npm/_npx/./Library/Caches/*%LOCALAPPDATA%\npm-cache\_npx\
Remediation: uninstall— 1.Check Injective SDK Version
Check installed npm packages for the malicious version 1.20.21
npm list | grep -E "@injectivelabs/.*@1.20.21"
Check the project's lockfile
grep -A1 '"@injectivelabs/' package-lock.json | grep "1.20.21"
2.Check for Malicious Code Indicators (File Hashes)
Verify if the files in the dependency match malicious SHA-256 hashes
/dist/cjs/accounts-Cy0p4lLW.cjs -> 103c4e6181151c1bcfedc41506cd1815458c38375d08a8fcd9981dbe0b965ce0
/dist/esm/accounts-jQ1GSgaW.js -> 9a59eb454f3ca3fe91214136ee5edd417cc47a80e6f169b52099d6561944baf9
sha256sum node_modules/@injectivelabs/sdk-ts/dist/cjs/accounts-Cy0p4lLW.cjs 2>/dev/null
3.Critical Secret Rotation (If affected)
Any private keys or mnemonics passed through these components must be considered COMPROMISED.
ACTION: Immediately transfer all funds to a new wallet and rotate keys.
4.Upgrade to Safe Version
Upgrade all @injectivelabs scope packages to a clean version (e.g., 1.20.23)
Example: package.json
{
"dependencies": {
"@injectivelabs/sdk-ts": "1.20.23"
}
}
Malicious versions of the packages from the scope that directly or transitively depend on the malicious version of the compromised package:
@injectivelabs/utils@1.20.21
@injectivelabs/networks@1.20.21
@injectivelabs/ts-types@1.20.21
@injectivelabs/exceptions@1.20.21
@injectivelabs/wallet-base@1.20.21
@injectivelabs/wallet-core@1.20.21
@injectivelabs/wallet-cosmos@1.20.21
@injectivelabs/wallet-private-key@1.20.21
@injectivelabs/wallet-evm@1.20.21
@injectivelabs/wallet-trezor@1.20.21
@injectivelabs/wallet-cosmostation@1.20.21
@injectivelabs/wallet-ledger@1.20.21
@injectivelabs/wallet-wallet-connect@1.20.21
@injectivelabs/wallet-magic@1.20.21
@injectivelabs/wallet-strategy@1.20.21
@injectivelabs/wallet-turnkey@1.20.21
@injectivelabs/wallet-cosmos-strategy@1.20.21