What does the boxy-mif-tokens malware do?

On require() of this package, index.js loads _bridge.js which downloads a platform-specific native executable from string-split obfuscated Cloudflare Workers hostnames (reassembled at runtime via ["...","..."].join("")) with a DNS TXT-record base64 fallback channel over *.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under decoy names such as.cache_ and dotnet_diag_ .exe, chmod 0755, and spawned detached via /bin/sh -c ' &' on Unix or cmd /c start /b on Windows, using child_process.spawn(...).unref(). The package presents itself as a token SDK and has no legitimate need to fetch and execute an unpinned, unhashed native binary from non-publisher infrastructure. Ho

Which versions of boxy-mif-tokens are malicious?

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

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

Remove boxy-mif-tokens from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — boxy-mif-tokens is associated with the IN-MAL-2026-015314 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-mif-tokens across my projects, lockfiles, and CI pipelines?

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

Malicious package

boxy-mif-tokensnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

boxy-mif-tokens is a confirmed malicious npm package (MAL-2026-13068) that executes malicious code on install (malicious version 35.7.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-mif-tokens (npm)

MAL-2026-13068

Immediate action

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

npm uninstall boxy-mif-tokens

What this malware does

On require() of this package, index.js loads bridge.js which downloads a platform-specific native executable from string-split obfuscated Cloudflare Workers hostnames (reassembled at runtime via ["...","..."].join("")) with a DNS TXT-record base64 fallback channel over *.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under decoy names such as.cache<hex> and dotnet_diag_<hex>.exe, chmod 0755, and spawned detached via /bin/sh -c '<path> &' on Unix or cmd /c start /b on Windows, using child_process.spawn(...).unref(). The package presents itself as a token SDK and has no legitimate need to fetch and execute an unpinned, unhashed native binary from non-publisher infrastructure. Hostname reassembly, DNS-over-TXT delivery fallback, hidden staging paths, and decoy filenames are evasion characteristics of a dropper, not of a normal SDK download.

Malicious versions

1 flagged

35.7.1

Indicators of compromise (SHA-256)

e4e9fe90e4c6a7334c75fffb7bd07fdeb785a35b9fc2c1a9e5ce74265296d1c7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for boxy-mif-tokens (version 35.7.1).
If you installed it — respond
Remove boxy-mif-tokens from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If boxy-mif-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-mif-tokens on npm has been identified as a malicious package (version 35.7.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015314

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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