Which versions of boxy-maker are malicious?

The following npm versions of boxy-maker are flagged malicious: 35.4.8. Treat any of these as compromised.

How do I remediate boxy-maker if I installed it?

boxy-maker 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.

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

If boxy-maker 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.

Is boxy-maker part of a known attack campaign?

Yes — boxy-maker is associated with the IN-MAL-2026-015327 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-maker across my projects, lockfiles, and CI pipelines?

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

Malicious package

boxy-makernpm

boxy-maker is a confirmed malicious npm package (MAL-2026-13057) that steals credentials and exfiltrates sensitive data (malicious version 35.4.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-maker (npm)

MAL-2026-13057

Immediate action

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

npm uninstall boxy-maker

What this malware does

On require() of the package, bridge.js downloads a platform-specific binary from obfuscated Cloudflare workers.dev hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev), writes it to a disguised temp path (e.g. dotnet_diag.exe,.cache_), chmods 0755 on non-Windows, and spawns it detached via /bin/sh -c or cmd. Destination hostnames are reassembled at runtime from split-string arrays (e.g. ['oob-worker.cf102','-baf.workers.d','ev'].join('')) to evade static scanners. If HTTPS fetch fails, bridge.js falls back to a DNS TXT covert channel under wel1.ru subdomains (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), reconstructing chunked base64-encoded payload bytes from TXT records, writing them to disk, and executing them. Cover-story framing (DISABLE_TELEMETRY env var, analytics_state, dotnet_diag* file names) misrepresents the behavior as CDN telemetry. Installing or importing this package executes attacker-controlled bytes on the host.

Malicious versions

1 flagged

35.4.8

Indicators of compromise (SHA-256)

1164ada14e000c3802b5766cdd31ef169e8f15a6d132cbe52d88b0c593b03c2a

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-maker (version 35.4.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-maker across your stack and pipelines.
If you installed it — respond
boxy-maker 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 boxy-maker 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 boxy-maker 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. boxy-maker on npm has been identified as a malicious package (version 35.4.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015327

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-maker-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database