Which versions of boxy-contract are malicious?

The following npm versions of boxy-contract are flagged malicious: 35.4.3. Treat any of these as compromised.

How do I remediate boxy-contract if I installed it?

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

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

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

Malicious package

boxy-contractnpm

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

Malicious code in boxy-contract (npm)

MAL-2026-13034

Immediate action

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

npm uninstall boxy-contract

What this malware does

On require() of boxy-contract, index.js loads init.js which selects a platform-specific endpoint and downloads a binary over HTTPS from string-concatenated Cloudflare Workers hostnames (oob-worker.cf102-baf.workers.dev, cf99-9b3.workers.dev, cf103-070.workers.dev), with a DNS-TXT fallback under *.dl.wel1.ru. The downloaded bytes are written to /tmp or %TEMP% under disguised names such as dotnet_diag<hex>.exe and.cache_<hex>, chmod'd to 0755, and spawned detached via spawn("/bin/sh", ["-c", fp+" &"], {detached:true}) or cmd.exe /c start /b. Destination hostnames and dangerous API names (child_process, chmodSync) are assembled from fragmented literals joined at runtime to evade static analysis. A DISABLE_TELEMETRY environment gate and cover-story naming (.analytics_state marker, dotnet_diag_ filenames) present the behavior as diagnostics but do not represent user-consented telemetry. The dropped binary is an opaque, unpinned, unverified native executable from attacker-controlled infrastructure, granting arbitrary code execution on the installer's host on plain npm install / require.

Malicious versions

1 flagged

35.4.3

Indicators of compromise (SHA-256)

01882c522b96942398bba4079e225224c0672793444cb1a8ce700d3441848ee5

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

Campaign

IN-MAL-2026-015354

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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