Malicious code in chain-api-sdk (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (0cc73eb727778c3a543bdef1f6993d4c8be38da047fc97b7a0614bd195590249) chain-api-sdk presents itself as the upstream multichain-crypto-wallet library: README, badges, package.json repository.url, and homepage all point to github.com/iamnotstatic/multichain-crypto-wallet, and the public API re-exports that project's wallet primitives (createWallet, transfer, private-key handling, mnemonic generation, encrypted-JSON keystore operations). The npm name differs from the upstream, so consumers who install chain-api-sdk believing they are using the legitimate library are routed to this fork. The fork's main entry (dist/index.js) unconditionally `require`s `mchain-sdk` and re-exports its `mci` and `multiChainInterface` symbols; package.json pins `mchain-sdk: ^4.2.5`. The upstream multichain-crypto-wallet does not depend on mchain-sdk. Because mchain-sdk is loaded on any `require('chain-api-sdk')`, whatever code ships in mchain-sdk executes inside the installer's Node.js process at library-load time, in a wallet library that handles private keys, mnemonics, and keystore data. The combination of upstream impersonation plus an undocumented, name-similar transitive that runs at import inside a wallet context is the delivery-vector shape of a dependency-chain dropper. ## Source: ghsa-malware (4948d6f7945e11f2d42e5ad5bb9fe577678ed57e1acb9ef244858ad572022543) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
The chain-api-sdk package masquerades as the upstream multichain-crypto-wallet library by copying its README, badges, repository URL, and homepage. Unlike the legitimate library, it depends on a malicious package, mchain-sdk, which executes code immediately upon import. This behavior occurs in a sensitive wallet environment handling private keys and mnemonic data, making it a dependency-chain dropper. The malicious code can fully compromise any system where the package is installed, risking all stored secrets and keys. The affected versions are 0.2.10, 0.2.11, and 0.2.12. There is no CVSS score or known exploits in the wild reported yet.
Potential Impact
Systems with chain-api-sdk versions 0.2.10, 0.2.11, or 0.2.12 installed should be considered fully compromised. The malicious code executes in the context of wallet operations, potentially exposing private keys, mnemonics, and encrypted keystore data. This can lead to complete loss of control over secrets and keys stored on the affected system.
Mitigation Recommendations
Remove the chain-api-sdk package immediately from all affected systems. Rotate all secrets and keys that were stored or managed on the compromised systems using a separate, trusted environment. Due to the high risk of full system compromise, assume that the attacker may have persistent access and take appropriate incident response measures. No official patch or fix is available; avoidance and removal are the only mitigations.
Malicious code in chain-api-sdk (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (0cc73eb727778c3a543bdef1f6993d4c8be38da047fc97b7a0614bd195590249) chain-api-sdk presents itself as the upstream multichain-crypto-wallet library: README, badges, package.json repository.url, and homepage all point to github.com/iamnotstatic/multichain-crypto-wallet, and the public API re-exports that project's wallet primitives (createWallet, transfer, private-key handling, mnemonic generation, encrypted-JSON keystore operations). The npm name differs from the upstream, so consumers who install chain-api-sdk believing they are using the legitimate library are routed to this fork. The fork's main entry (dist/index.js) unconditionally `require`s `mchain-sdk` and re-exports its `mci` and `multiChainInterface` symbols; package.json pins `mchain-sdk: ^4.2.5`. The upstream multichain-crypto-wallet does not depend on mchain-sdk. Because mchain-sdk is loaded on any `require('chain-api-sdk')`, whatever code ships in mchain-sdk executes inside the installer's Node.js process at library-load time, in a wallet library that handles private keys, mnemonics, and keystore data. The combination of upstream impersonation plus an undocumented, name-similar transitive that runs at import inside a wallet context is the delivery-vector shape of a dependency-chain dropper. ## Source: ghsa-malware (4948d6f7945e11f2d42e5ad5bb9fe577678ed57e1acb9ef244858ad572022543) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The chain-api-sdk package masquerades as the upstream multichain-crypto-wallet library by copying its README, badges, repository URL, and homepage. Unlike the legitimate library, it depends on a malicious package, mchain-sdk, which executes code immediately upon import. This behavior occurs in a sensitive wallet environment handling private keys and mnemonic data, making it a dependency-chain dropper. The malicious code can fully compromise any system where the package is installed, risking all stored secrets and keys. The affected versions are 0.2.10, 0.2.11, and 0.2.12. There is no CVSS score or known exploits in the wild reported yet.
Potential Impact
Systems with chain-api-sdk versions 0.2.10, 0.2.11, or 0.2.12 installed should be considered fully compromised. The malicious code executes in the context of wallet operations, potentially exposing private keys, mnemonics, and encrypted keystore data. This can lead to complete loss of control over secrets and keys stored on the affected system.
Mitigation Recommendations
Remove the chain-api-sdk package immediately from all affected systems. Rotate all secrets and keys that were stored or managed on the compromised systems using a separate, trusted environment. Due to the high risk of full system compromise, assume that the attacker may have persistent access and take appropriate incident response measures. No official patch or fix is available; avoidance and removal are the only mitigations.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10009
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-6vrp-3g92-phhf"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50ba5068715ace4357ebc5
Added to database: 07/10/2026, 09:24:32 UTC
Last enriched: 07/10/2026, 09:40:54 UTC
Last updated: 07/30/2026, 22:05:36 UTC
Views: 29
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.