What does the boxy-sticky-providers malware do?

On require() of the package, _init.js downloads a platform-specific binary from Cloudflare Workers hosts whose names are reassembled at runtime from split-string arrays (oob-worker.cf101-adf.workers.dev), with a DNS-TXT covert-channel fallback via sdk.dl.wel1.ru. The payload is staged to /var/tmp/.cache_ on Unix or a dotnet_diag_ .exe path on Windows, chmod 0755'd, and spawned detached through /bin/sh -c or cmd /c start. There is no hash or signature verification, the destinations are unrelated to any declared publisher, and the code uses disguised filenames, cooldown markers, and DISABLE_TELEMETRY/DO_NOT_TRACK kill-switches. Anyone who installs and require()s this package executes

Which versions of boxy-sticky-providers are malicious?

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

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

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

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

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

Malicious package

boxy-sticky-providersnpm

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

Malicious code in boxy-sticky-providers (npm)

MAL-2026-13084

Immediate action

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

npm uninstall boxy-sticky-providers

What this malware does

On require() of the package, init.js downloads a platform-specific binary from Cloudflare Workers hosts whose names are reassembled at runtime from split-string arrays (oob-worker.cf101-adf.workers.dev), with a DNS-TXT covert-channel fallback via sdk.dl.wel1.ru. The payload is staged to /var/tmp/.cache<hex> on Unix or a dotnet_diag_<hex>.exe path on Windows, chmod 0755'd, and spawned detached through /bin/sh -c or cmd /c start. There is no hash or signature verification, the destinations are unrelated to any declared publisher, and the code uses disguised filenames, cooldown markers, and DISABLE_TELEMETRY/DO_NOT_TRACK kill-switches. Anyone who installs and require()s this package executes attacker-controlled bytes on their machine.

Malicious versions

1 flagged

35.1.5

Indicators of compromise (SHA-256)

cc08631cb79f90d5440020f420e9c7ad9e67ec84f25f085825c5b5f600f613a4

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

Campaign

IN-MAL-2026-015307

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-sticky-providers-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