Which versions of boxy-use-calls are malicious?

The following npm versions of boxy-use-calls are flagged malicious: 35.1.8. Treat any of these as compromised.

How do I remediate boxy-use-calls if I installed it?

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

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

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

Malicious package

boxy-use-callsnpm

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

Malicious code in boxy-use-calls (npm)

MAL-2026-13094

Immediate action

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

npm uninstall boxy-use-calls

What this malware does

index.js unconditionally requires bridge.js, whose top-level main() runs on import. bridge.js selects a platform-specific payload path, downloads an opaque binary via https.get from one of several string-split Cloudflare-Workers hosts assembled by.join('') (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev), writes it to a disguised filename under /tmp or %TEMP% (e.g..cache<hex>, dotnet_diag<hex>.exe), chmods it 0755, and detached-spawns it via /bin/sh -c or cmd /c start with.unref(). A fallback channel queries DNS TXT records under c.<domain> and sequentially-numbered subdomains of *.dl.wel1.ru to reassemble a base64-chunked payload when HTTPS is blocked. A 21376-second replay-suppression stamp is written under an 'analytics_state' key. No pinning, no signature check, no publisher-matching source. A separate lib/telemetry.js file presents an 81 KB 'analytics SDK' that is never referenced by index.js or _bridge.js and shares DISABLE_TELEMETRY/ANALYTICS_OPT_OUT env-var names with _bridge.js, serving as cover-story camouflage for the dropper.

Malicious versions

1 flagged

35.1.8

Indicators of compromise (SHA-256)

41e7b8d0b1d87131f56439454c512c68c367ed421c04c7a4bc165c7aeb6acdd6

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

Campaign

IN-MAL-2026-015280

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-use-calls-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