Which versions of boxy-tokens are malicious?

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

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

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

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

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

Malicious package

boxy-tokensnpm

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

Malicious code in boxy-tokens (npm)

MAL-2026-13092

Immediate action

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

npm uninstall boxy-tokens

What this malware does

index.js unconditionally requires./setup.js on module load. setup.js assembles Cloudflare Workers hostnames from split-string arrays (oob-worker.cf1-01-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev), selects a platform-specific asset (linux_x64, linux_arm64, darwin, win32), downloads an opaque binary via https.get, writes it to /var/tmp/.cache_<rnd> or %TEMP%\dotnet_diag_<rnd>.exe, chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start with no hash or signature verification. A DNS-TXT fallback channel reconstructs *.dl.wel1.ru from a split array, reads a chunk count from c.<domain>, fetches N base64-encoded TXT records from numbered subdomains, and concatenates them into an executable buffer that is executed the same way. Filenames impersonate dotnet diagnostic artifacts and cache files. Any consumer that requires boxy-tokens runs the attacker's binary on their host.

Malicious versions

1 flagged

35.5.2

Indicators of compromise (SHA-256)

bfb29953971bb0c3eae94e97f7a9efe132bd4a954252ae52c989f990f389d098

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

Campaign

IN-MAL-2026-015298

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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