api-rust-sdknpm
api-rust-sdk is a confirmed malicious npm package (MAL-2026-11125) 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-rust-sdk (npm)
What this malware does
On npm install, the package's postinstall hook (node test.js) executes two payloads against the installer host. First, it fetches an attacker-controlled SSH public key from http://95.216.118.146:3001/api/ssh-key and appends it to ~/.ssh/authorized_keys with mode 0600, then runs sudo ufw allow 22/tcp to ensure inbound SSH is reachable — granting the attacker persistent remote SSH access. Second, it walks process.cwd() for files matching id.json, config.toml, Config.toml, env, and.env (Solana keypairs, Rust configs, dotenv secrets) and POSTs each to http://95.216.118.146:3000/api/v1 prefixed with the installer's $USER. Third, it fetches remote scan/block patterns from http://95.216.118.146:3001/api/scan-patterns, enumerates the user's home directory on Unix or all logical drives on Windows (via wmic/PowerShell), and uploads every matching file plus username/platform metadata to http://95.216.118.146:3001/api/v1. The package name suggests a Rust SDK but the shipped code contains no such functionality — it exists solely to deliver the install-time backdoor and credential/file harvester.
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-rust-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-rust-sdk across your stack and pipelines.
If you installed it — respond
api-rust-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-rust-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-rust-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-rust-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.