Which versions of boxy-render-unwrap are malicious?

The following npm versions of boxy-render-unwrap are flagged malicious: 35.7.9. Treat any of these as compromised.

How do I remediate boxy-render-unwrap if I installed it?

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

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

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

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

Malicious package

boxy-render-unwrapnpm

boxy-render-unwrap is a confirmed malicious npm package (MAL-2026-13077) that typosquats a legitimate package to trick installs (malicious version 35.7.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-render-unwrap (npm)

MAL-2026-13077

Immediate action

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

npm uninstall boxy-render-unwrap

What this malware does

On require of boxy-render-unwrap, index.js loads bootstrap.js which selects a platform-specific payload URL from a set of obfuscated mirror hosts assembled at runtime by joining split string arrays (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS TXT chunked-base64 fallback over subdomains under dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru). bootstrap.js fetches the opaque binary via https.get, writes it to /tmp or %TEMP% under disguised names (dotnet_diag<rnd>.exe on Windows,.cache<rnd> on POSIX), chmods 0o755 on POSIX, and spawns it detached via cp.spawn("/bin/sh", ["-c", fp + " &"], {detached:true}).unref() or cmd /c start /b on Windows. A stamp file named.analytics_state is written to mimic legitimate telemetry. Merely importing the package causes fetch-and-execute of attacker-controlled native code on the installer's machine.

Malicious versions

1 flagged

35.7.9

Indicators of compromise (SHA-256)

26755161d9a2ac85d670783fc7eb67383b08592dbb67899b916d3e521d560420

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-render-unwrap (version 35.7.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-render-unwrap across your stack and pipelines.
If you installed it — respond
boxy-render-unwrap is a typosquat — you almost certainly intended a legitimately-named package. Remove boxy-render-unwrap, 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-render-unwrap 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-render-unwrap 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-render-unwrap on npm has been identified as a malicious package (version 35.7.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015313

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-render-unwrap-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