snavboxnpm
snavbox is a confirmed malicious npm package (MAL-2025-49362) that executes malicious code on install (malicious versions 1.0.0, 1.0.2, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in snavbox (npm)
What this malware does
At CLI startup, index.js downloads three native shared libraries (sbx.so, bot.so, v1.so) from https://${arch}.31888.xyz/ (amd64.31888.xyz, arm64.31888.xyz), writes them to disk, and loads them via koffi.load() to invoke native functions from the fetched bytes. The download URL is not version-pinned, the domain is unrelated to the package publisher, and the downloadLibrary(url, fileName, expectedSha256) helper treats an empty expectedSha256 as a pass, so no integrity check is performed. Package metadata describes the project as "WildGuard - Protect Our Wildlife" with an accompanying wildlife-themed index.html, but the actual code implements a sing-box multi-protocol proxy (vless/vmess/trojan/hysteria2/tuic/reality/anytls), a Cloudflare Argo tunnel configured with noTLSVerify: true, a Nezha remote-management agent, and a hardcoded keep-alive callback to https://keep.gvrander.eu.org/add-url. Multiple execSync('curl...') invocations are also present. The mismatch between the advertised purpose and the shipped behavior, combined with the unpinned unverified native-code fetch from a non-publisher host, gives the operator of 31888.xyz arbitrary code execution on any host that runs this package.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
The OpenSSF Package Analysis project identified 'snavbox' @ 1.0.0 (npm) as malicious.
It is considered malicious because:
- The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for snavbox (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging snavbox across your stack and pipelines.
If you installed it — respond
Remove snavbox from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If snavbox 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 snavbox 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
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks snavbox-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.