Which versions of boxy-deps-calculator are malicious?

The following npm versions of boxy-deps-calculator are flagged malicious: 35.9.5. Treat any of these as compromised.

How do I remediate boxy-deps-calculator if I installed it?

boxy-deps-calculator 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.

I already installed boxy-deps-calculator — how do I know if it already compromised me?

If boxy-deps-calculator was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is boxy-deps-calculator part of a known attack campaign?

Yes — boxy-deps-calculator is associated with the IN-MAL-2026-015337 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find boxy-deps-calculator across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for boxy-deps-calculator (version 35.9.5).

Malicious package

boxy-deps-calculatornpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

boxy-deps-calculator is a confirmed malicious npm package (MAL-2026-13038) that opens a backdoor for remote access (malicious version 35.9.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-deps-calculator (npm)

MAL-2026-13038

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall boxy-deps-calculator

What this malware does

setup.js runs at install time: it performs an HTTPS reconnaissance request (https.get to a remote host with an identifier payload) and then spawns a platform-specific shell (spawn("/bin/sh") on POSIX, spawn("cmd") on Windows) via child_process. The file is invoked as an npm lifecycle script, giving the remote-directed shell execution on installer machines with no user interaction beyond npm install. The combination of an install-time outbound HTTP callout plus unconditional shell spawn is a dropper/backdoor shape rather than any documented build behavior, and the package name (a lookalike of common dependency-related utilities) has no legitimate purpose requiring shell execution during install.

Malicious versions

1 flagged

35.9.5

Indicators of compromise (SHA-256)

1b0faa243ad4d8a3f6d3b76b94da84738fcd5a097efc0c2e920b4f029b76f970

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for boxy-deps-calculator (version 35.9.5).
If you installed it — respond
boxy-deps-calculator 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.
Did it already run?
If boxy-deps-calculator was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-015337

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-deps-calculator-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