Which versions of boxy-wrapper-webpack-plugin are malicious?

The following npm versions of boxy-wrapper-webpack-plugin are flagged malicious: 35.5.8. Treat any of these as compromised.

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

boxy-wrapper-webpack-plugin is a typosquat — you almost certainly intended a legitimately-named package. Remove boxy-wrapper-webpack-plugin, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed boxy-wrapper-webpack-plugin — how do I know if it already compromised me?

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

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

Malicious package

boxy-wrapper-webpack-pluginnpm

boxy-wrapper-webpack-plugin is a confirmed malicious npm package (MAL-2026-13099) that typosquats a legitimate package to trick installs (malicious version 35.5.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-wrapper-webpack-plugin (npm)

MAL-2026-13099

Immediate action

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

npm uninstall boxy-wrapper-webpack-plugin

What this malware does

The package's main entrypoint (index.js) unconditionally requires./compat.js, whose top-level main() reconstructs obfuscated Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev) and vendor-lookalike domains (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru) via array-join splits, downloads a platform-specific executable for linux/darwin/win32/arm64, writes it to /tmp or %TEMP% under a disguised name (e.g. dotnet_diag.exe,.cache_), chmods 0755, and detached-spawns it via /bin/sh -c or cmd /c start. A DNS-TXT chunked base64 channel is used as a fallback delivery path. A second, structurally identical dropper is bundled at lib/telemetry.js (~80KB): base64-decoded payload chunks, HTTPS transport with endpoint rotation, DNS service discovery, obfuscated child_process access via require("child_"+"process"), obfuscated permission change via fs["chmod"+"Sync"], and cp.spawn("/bin/sh", ["-c", filePath+" &"]). The lure is named to resemble a webpack plugin, and hostnames and API references are split across array joins to evade string-based scanners.

Malicious versions

1 flagged

35.5.8

Indicators of compromise (SHA-256)

835a7dd72392b1156dbab57a57b627982e490b3dbd2a4f772dea0b112b8c8a50

Detection & response playbook

Typosquat

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

Campaign

IN-MAL-2026-015276

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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