Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

volna-boxy-di-testnpm

volna-boxy-di-test is a confirmed malicious npm package (MAL-2026-12079) that opens a backdoor for remote access (malicious version 20.3.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in volna-boxy-di-test (npm)

MAL-2026-12079
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall volna-boxy-di-test

What this malware does

On require, index.js loads compat.js which selects a platform-specific payload path, reconstructs C2 hostnames at runtime from split string fragments joined with "" (including oob-worker.cf10*-*.workers.dev variants and a *.dl.well1.site DNS TXT chunked-base64 fallback), fetches unpinned unhashed bytes over HTTPS, writes them to /tmp or %TEMP% under disguising names such as.cache<hex> and dotnet_diag_<hex>.exe, chmods 0755 on Unix, and spawns the binary detached via /bin/sh -c or cmd. The User-Agent is spoofed to node-fetch/2.6 to blend with legitimate traffic, a TTL flag file (.analytics_state) suppresses re-execution, and env gates (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) plus cover-story comments ("telemetry", "analytics", "Skip in CI") mask the dropper. The package presents itself as a test harness; the fetched code, the hosts, and the disguised filenames do not match that stated purpose.

Malicious versions

1 flagged
20.3.8

Indicators of compromise (SHA-256)

caad3654d755de84a91ca9afc1d7d393a1e2868b54b0b03020780b7878df28f8

Detection & response playbook

Backdoor / remote access

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for volna-boxy-di-test (version 20.3.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging volna-boxy-di-test across your stack and pipelines.

  2. If you installed it — respond

    volna-boxy-di-test establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If volna-boxy-di-test 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.

  4. How O3 protects you

    O3 blocks volna-boxy-di-test 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

No. volna-boxy-di-test on npm has been identified as a malicious package (version 20.3.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011964

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks volna-boxy-di-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
volna-boxy-di-test (npm) malicious package — MAL-2026-12079 | O3 Security