crossmint-wallets-sdknpm
Malicious code in crossmint-wallets-sdk (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
Package name impersonates the Crossmint wallet SDK family. Both preinstall.js and index.js import child_process, capture host identifiers (hostname is read on line 7/9 respectively), and POST the collected data via https.request to a hardcoded external endpoint (line 12/23). The preinstall.js path fires automatically on npm install before any user code runs, giving the publisher install-time data exfiltration from any developer or build system that installs this package. The combination of child_process + hostname collection + outbound POST in a preinstall lifecycle script, in a package whose name typosquats a known wallet SDK, matches the active-attack credential/reconnaissance exfiltration fingerprint.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for crossmint-wallets-sdk (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging crossmint-wallets-sdk across your stack and pipelines.
If you installed it — respond
crossmint-wallets-sdk is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If crossmint-wallets-sdk was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks crossmint-wallets-sdk before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks crossmint-wallets-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.