Which versions of boxy-temper are malicious?

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

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

boxy-temper 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-temper — how do I know if it already compromised me?

If boxy-temper 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-temper part of a known attack campaign?

Yes — boxy-temper is associated with the IN-MAL-2026-015294 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-temper 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-temper (version 35.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-temper across your stack and pipelines.

Malicious package

boxy-tempernpm

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

Malicious code in boxy-temper (npm)

MAL-2026-13087

Immediate action

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

npm uninstall boxy-temper

What this malware does

index.js require()s bridge.js on module load. bridge.js selects a platform-specific URL from a list of Cloudflare Workers hostnames whose strings are assembled at runtime via Array.join('') (e.g. 'oob-worker.cf103-070.workers.dev', 'oob-worker.cf102-baf.workers.dev', 'oob-worker.cf99-9b3.workers.dev'), downloads an opaque binary over HTTPS, writes it to /tmp on unix or %TEMP% on windows under disguised names (.cache<hex>, dotnet_diag<hex>.exe), chmods 0755, and spawns it detached with stdio ignored via cp.spawn('/bin/sh', ['-c', fp+' &']) or the cmd equivalent. If the HTTPS fetch fails, the code falls back to a DNS-TXT covert channel, issuing chunked TXT queries to attacker-controlled subdomains under wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), base64-reassembles the responses into a binary, writes it to disk and executes it. Hostnames are split into fragments and joined at runtime specifically to evade static string matching, and opt-out env vars are labeled as 'analytics' as a cover story. The package's advertised purpose is a 'boxy temper microservice adapter' but the main class is a no-op stub; the only real behavior is the loader. No hash or signature verification is performed on the downloaded payload.

Malicious versions

1 flagged

35.1.5

Indicators of compromise (SHA-256)

b3410beb63f55222c2e4d1823fae16f5de4cc07ec2ba428712d482737c72bbd2

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-temper (version 35.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-temper across your stack and pipelines.
If you installed it — respond
boxy-temper 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-temper 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-temper 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-temper on npm has been identified as a malicious package (version 35.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015294

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-temper-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