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 a typosquat — you almost certainly intended a legitimately-named package. Remove boxy-tokens, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

If boxy-tokens was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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?

Search your lockfiles and build artifacts for boxy-tokens (version 35.5.2).

Malicious package

boxy-tokensnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

boxy-tokens is a confirmed malicious npm package (MAL-2026-13092) that typosquats a legitimate package to trick installs (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

Typosquat

Find it
Search your lockfiles and build artifacts for boxy-tokens (version 35.5.2).
If you installed it — respond
boxy-tokens is a typosquat — you almost certainly intended a legitimately-named package. Remove boxy-tokens, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If boxy-tokens was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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 malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database