Which versions of boxy-add-script are malicious?

The following npm versions of boxy-add-script are flagged malicious: 35.2.2. Treat any of these as compromised.

How do I remediate boxy-add-script if I installed it?

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

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

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

Search your lockfiles and build artifacts for boxy-add-script (version 35.2.2).

Malicious package

boxy-add-scriptnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

boxy-add-script is a confirmed malicious npm package (MAL-2026-13030) that executes malicious code on install (malicious version 35.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-add-script (npm)

MAL-2026-13030

Immediate action

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

npm uninstall boxy-add-script

What this malware does

On require('boxy-add-script'), index.js loads polyfill.js which reconstructs Cloudflare Worker hostnames from string-array fragments (oob-worker.cf103-070.workers.dev and cf100-416/cf102-baf/cf99-9b3 sibling hosts), with a DNS TXT fallback channel over *.dl.wel1.ru that reassembles a base64 payload. polyfill.js downloads a platform-specific binary over https, writes it to /var/tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag<hex>.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. Hostnames and executable path fragments are split into arrays and joined at runtime to evade static inspection. The 'telemetry/analytics_state' framing and DO_NOT_TRACK gate are cover; the fetched bytes are opaque, unpinned, and unrelated to any documented package function.

Malicious versions

1 flagged

35.2.2

Indicators of compromise (SHA-256)

85a91c45a1de3e17ac4c6595c6eac76736684ef353e3040a3e82b42e76911952

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for boxy-add-script (version 35.2.2).
If you installed it — respond
Remove boxy-add-script 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-add-script 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-add-script on npm has been identified as a malicious package (version 35.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015360

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-add-script-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