Which versions of boxy-demo-tokens are malicious?

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

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

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

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

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

Malicious package

boxy-demo-tokensnpm

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

Malicious code in boxy-demo-tokens (npm)

MAL-2026-13037

Immediate action

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

npm uninstall boxy-demo-tokens

What this malware does

On require(), index.js loads bridge.js which fetches a platform-specific executable from Cloudflare Workers subdomains whose hostnames are reassembled from split string arrays (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev). The fetched bytes are written to /tmp or %TEMP% under disguising names (.cache<hex>, dotnet_diag_<hex>.exe), chmodded 0755, and spawned as a detached child process via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}) or the Windows equivalent. If the HTTPS fetch fails, _bridge.js falls back to a DNS-TXT covert channel at *.dl.wel1.ru subdomains (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru): a count is read from c.<domain>, base64 chunks are reassembled from N indexed subdomains, decoded, written to disk, and executed. String-split hostname assembly and cover-story comments referencing DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK environment variables are used to evade static scanners. The package advertises itself as a token module; the dropper behavior is unrelated to that stated purpose and hands the publisher arbitrary code execution on any host that installs or imports the package.

Malicious versions

1 flagged

35.2.7

Indicators of compromise (SHA-256)

a4fef0cd8b9f91923e6bf6bf357c229e57bb3b108b48ddc3bc9f0faa8f16b8db

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

Campaign

IN-MAL-2026-015339

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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