api-rs-tuilsnpm
api-rs-tuils is a confirmed malicious npm package (MAL-2026-14256) that typosquats a legitimate package to trick installs (malicious version 2.1.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in api-rs-tuils (npm)
What this malware does
[email protected] runs a malicious postinstall hook (node test.js) that executes obfuscated code in index.js against the installer's machine. The code (1) fetches an attacker SSH public key from http://170.205.31.203:3001/api/ssh-key and appends it to ~/.ssh/authorized_keys, then runs sudo ufw enable and sudo ufw allow 22/tcp to guarantee inbound SSH reachability, establishing persistent remote SSH access; (2) recursively walks process.cwd() collecting files matching id.json, config.toml, Config.toml, env, and.env and POSTs their contents (prefixed with $USER) to http://170.205.31.203:3000/api/v1; (3) fetches attacker-supplied scan patterns from http://170.205.31.203:3001/api/scan-patterns and crawls os.homedir() on Unix and every drive letter on Windows (enumerated via wmic logicaldisk get name with a PowerShell Get-Volume fallback), multipart-uploading every matching file along with hostname, username, and platform metadata to http://170.205.31.203:3001/api/v1. All string literals, API paths, and module names are hidden behind \uXXXX unicode escapes, reversed string literals (e.g. "1v/ipa/0003:302.13.502.031.502.071//:ptth".split('').reverse().join('')), and XOR/arithmetic dead code. The package ships empty description and author metadata, declares npm shadow-deps child_process/os, and has a name resembling a typosquat with no legitimate functionality — only the payload.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for api-rs-tuils (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-rs-tuils across your stack and pipelines.
If you installed it — respond
api-rs-tuils is a typosquat — you almost certainly intended a legitimately-named package. Remove api-rs-tuils, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If api-rs-tuils 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-rs-tuils 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-rs-tuils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.