Which versions of boxy-global-modules-webpack-plugin are malicious?

The following npm versions of boxy-global-modules-webpack-plugin are flagged malicious: 35.5.5. Treat any of these as compromised.

How do I remediate boxy-global-modules-webpack-plugin if I installed it?

Remove boxy-global-modules-webpack-plugin 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-global-modules-webpack-plugin — how do I know if it already compromised me?

If boxy-global-modules-webpack-plugin 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-global-modules-webpack-plugin part of a known attack campaign?

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

Malicious package

boxy-global-modules-webpack-pluginnpm

boxy-global-modules-webpack-plugin is a confirmed malicious npm package (MAL-2026-13050) that executes malicious code on install (malicious version 35.5.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-global-modules-webpack-plugin (npm)

MAL-2026-13050

Immediate action

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

npm uninstall boxy-global-modules-webpack-plugin

What this malware does

On require of the package's main entry, loader.js immediately fetches a platform-specific opaque binary over HTTPS from hardcoded Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS TXT fallback under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. Host and API strings are reassembled at runtime by array-join from split fragments (e.g. ["oob-worker.cf103-070.workers.de","v"].join(""), ['sdk.dl.wel','1.ru'].join(""), "chmod"+"Sync") to evade static matching. The fetched bytes are written to /tmp or %TEMP% under a disguised name (.cache<hex> or dotnet_diag_<hex>.exe), chmod 755 is applied on POSIX, and the file is spawned detached via /bin/sh -c or cmd.exe with.unref(). No hash or signature verification is performed and the destinations are unrelated to any legitimate publisher of this package. In addition, lib/telemetry.js (81 KB) ships a structurally identical secondary dropper (HttpTransport, DNS-based service discovery, base64 chunk reassembly, spawn /bin/sh on a downloaded path, chmod 755 via string-concatenated API name) that is not reached from index.js in this version but is present in the tarball.

Malicious versions

1 flagged

35.5.5

Indicators of compromise (SHA-256)

6ce609c23d8c990c21c16692270dbb62589c6f63e716994c31e5ed4f466dcad7

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-global-modules-webpack-plugin (version 35.5.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-global-modules-webpack-plugin across your stack and pipelines.
If you installed it — respond
Remove boxy-global-modules-webpack-plugin 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-global-modules-webpack-plugin 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-global-modules-webpack-plugin 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-global-modules-webpack-plugin on npm has been identified as a malicious package (version 35.5.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015320

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-global-modules-webpack-plugin-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