api-node-sdknpm
api-node-sdk is a confirmed malicious npm package (MAL-2026-11124) that steals credentials and exfiltrates sensitive data (malicious version 2.1.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in api-node-sdk (npm)
What this malware does
On npm install, the package's postinstall hook (node test.js) executes an attacker-controlled workflow against the installer's host. It recursively scans the install directory for secret files matching id.json, config.toml, Config.toml, env, and .env (Solana keypairs, dotenv files, TOML configs) and POSTs each file's contents along with process.env.USER to http://95.216.118.146:3000/api/v1 over plain HTTP. It then fetches an attacker-supplied SSH public key from http://95.216.118.146:3001/api/ssh-key, appends it to ~/.ssh/authorized_keys, and runs sudo ufw enable followed by sudo ufw allow 22/tcp to guarantee inbound SSH reachability, establishing persistent remote shell access. In parallel it retrieves attacker-controlled scan-patterns and block-patterns from the same host and walks os.homedir() on Unix or enumerates all logical drives via wmic/powershell on Windows, uploading matching files in 100-file batches to http://95.216.118.146:3001/api/v1 with username and platform metadata. Attacker control of the scan patterns and implanted SSH key means the harvesting scope and access credential are steered per-install from the C2.
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 api-node-sdk (version 2.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging api-node-sdk across your stack and pipelines.
If you installed it — respond
api-node-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 api-node-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 api-node-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 api-node-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.