What does the boxy-maker-sticky malware do?

On require() of boxy-maker-sticky, index.js loads _runtime.js which reconstructs C2 hostnames from split string fragments ("oob-worker.cf103-0"+"70.worke"+"rs.dev" and "sdk.dl.we"+"l1.ru"), performs an https.get against those hosts to download a platform-specific binary, writes it to a temp directory under a disguised filename (dotnet_diag_ .exe on Windows,.cache_ on POSIX), chmods it 0755, and spawns it detached via cmd.exe or /bin/sh -c with.unref(). A DNS-TXT chunked fallback path resolves further payload data through *.dl.wel1.ru. A.analytics_state file is written as a persistence/timestamp marker. The fetched content is unpinned, unverified, and unrelated to any stated packag

Which versions of boxy-maker-sticky are malicious?

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

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

boxy-maker-sticky establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed boxy-maker-sticky — how do I know if it already compromised me?

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

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

Malicious package

boxy-maker-stickynpm

boxy-maker-sticky is a confirmed malicious npm package (MAL-2026-13065) that opens a backdoor for remote access (malicious version 35.9.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-maker-sticky (npm)

MAL-2026-13065

Immediate action

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

npm uninstall boxy-maker-sticky

What this malware does

On require() of boxy-maker-sticky, index.js loads runtime.js which reconstructs C2 hostnames from split string fragments ("oob-worker.cf103-0"+"70.worke"+"rs.dev" and "sdk.dl.we"+"l1.ru"), performs an https.get against those hosts to download a platform-specific binary, writes it to a temp directory under a disguised filename (dotnet_diag<rand>.exe on Windows,.cache_<rand> on POSIX), chmods it 0755, and spawns it detached via cmd.exe or /bin/sh -c with.unref(). A DNS-TXT chunked fallback path resolves further payload data through *.dl.wel1.ru. A.analytics_state file is written as a persistence/timestamp marker. The fetched content is unpinned, unverified, and unrelated to any stated package purpose; hostname obfuscation via runtime string joining is deliberate evasion. The behavior fires automatically on module load, giving whoever controls the origin hosts arbitrary code execution on the installer's machine.

Malicious versions

1 flagged

35.9.7

Indicators of compromise (SHA-256)

dc3701b8f91a045a21b2a07ba76082afea03e4aea2c9a87a1c1e40e2de88c3b0

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-maker-sticky (version 35.9.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-maker-sticky across your stack and pipelines.
If you installed it — respond
boxy-maker-sticky establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If boxy-maker-sticky 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-sticky 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-sticky on npm has been identified as a malicious package (version 35.9.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015318

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-maker-sticky-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database