Which versions of boxy-devtools-tokens are malicious?

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

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

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

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

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

Malicious package

boxy-devtools-tokensnpm

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

Malicious code in boxy-devtools-tokens (npm)

MAL-2026-13040

Immediate action

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

npm uninstall boxy-devtools-tokens

What this malware does

The package's main entry (index.js) unconditionally loads _compat.js on require(). _compat.js assembles a rotating list of Cloudflare Workers hostnames (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) from split string fragments joined via.join(''), with a DNS TXT fallback channel (c.<domain>/N.<domain> under *.dl.wel1.ru) used when HTTPS delivery is blocked. It downloads a platform-specific binary via https.get, writes it to a temp file with a disguised name, chmods it 0755 on Unix, and spawns it detached via spawn('/bin/sh',...) or spawn('cmd',...). An mtime stamp file suppresses re-execution, and environment variables named to resemble opt-out signals (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) gate execution. The package is advertised as a token library; the shipped code performs an out-of-band binary drop from attacker-controlled infrastructure with no relationship to that purpose.

Malicious versions

1 flagged

35.9.9

Indicators of compromise (SHA-256)

902a7b42df643551615d55958546ab9115082ac8eb60ff1208cafa18b804ab3c

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

Campaign

IN-MAL-2026-015343

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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