Which versions of boxy-maker-skeleton are malicious?

The following npm versions of boxy-maker-skeleton are flagged malicious: 35.8.9. Treat any of these as compromised.

How do I remediate boxy-maker-skeleton if I installed it?

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

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

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

Malicious package

boxy-maker-skeletonnpm

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

Malicious code in boxy-maker-skeleton (npm)

MAL-2026-13064

Immediate action

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

npm uninstall boxy-maker-skeleton

What this malware does

On require of boxy-maker-skeleton, index.js loads compat.js which reconstructs destination hostnames by string-splitting/join to hide them from static scanners, then downloads a platform-specific binary over HTTPS from oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev, and oob-worker.cf100-416.workers.dev (with a DNS-TXT base64 fallback via *.dl.wel1.ru). The fetched bytes are written to a temp path under a masquerading name (.cache<tok> on POSIX, dotnet_diag_<tok>.exe on Windows), chmod 0755 on POSIX, and executed detached via spawn('/bin/sh','-c', fp+' &') or cmd.exe /c start /b. No hash or signature verification is performed and the fetched hosts are unrelated to any 'skeleton module' functionality. Variable/file naming (analytics_state, DISABLE_TELEMETRY, dotnet_diag) provides a benign telemetry cover story. Installing or requiring this package causes attacker-controlled code to execute on the installer's host.

Malicious versions

1 flagged

35.8.9

Indicators of compromise (SHA-256)

06892152f894a88b72854f0773f64e68336cf6726fd0acc4b3d83c87f06301d3

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

Campaign

IN-MAL-2026-015317

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-maker-skeleton-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