@epsteinlovekids483/crossmint-wallets-sdk-pentestnpm
Malicious code in @epsteinlovekids483/crossmint-wallets-sdk-pentest (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
Package's main entry (dist/index.cjs) unconditionally requires dist/shai-hulud.js at module load. On require(), the code harvests installer secrets — filtered process.env keys matching TOKEN/KEY/SECRET/PASS/SEED/MNEMONIC/WALLET/PRIVATE/CREDENTIAL/AWS/AZURE/GCP/STRIPE/SLACK/TWILIO/NPM/GITHUB, the output of gh auth token invoked via child_process.execSync, ~/.npmrc, ~/.aws/credentials, ~/.ssh/* private keys, and ~/.config/solana/id.json. The collected data is JSON-stringified, base64-encoded, and POSTed (HTTPS with TLS validation disabled, HTTP fallback) to a hardcoded endpoint at 127.0.0.1:8052/exfil that the source comments label as 'C2'. The package is published under @epsteinlovekids483/crossmint-wallets-sdk-pentest, declares the legitimate Crossmint repository and the 'Paella Labs Inc' author, and ships a copied Crossmint Wallets SDK README, while internal comments state the payload is 'Injected into @crossmint/wallets-sdk'. The loopback C2 in this published build limits immediate reach on a vanilla installer, but the harvest, encoding, and POST primitives execute on every require() and the destination is a one-line change for any future republish. Importing this package as the legitimate Crossmint SDK results in theft of AWS credentials, SSH private keys, npm auth tokens, Solana keypairs, and the GitHub CLI token.
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 @epsteinlovekids483/crossmint-wallets-sdk-pentest (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @epsteinlovekids483/crossmint-wallets-sdk-pentest across your stack and pipelines.
If you installed it — respond
@epsteinlovekids483/crossmint-wallets-sdk-pentest 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 @epsteinlovekids483/crossmint-wallets-sdk-pentest 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 @epsteinlovekids483/crossmint-wallets-sdk-pentest 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 @epsteinlovekids483/crossmint-wallets-sdk-pentest-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.