Which versions of boxy-maker-scroll are malicious?

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

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

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

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

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

Malicious package

boxy-maker-scrollnpm

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

Malicious code in boxy-maker-scroll (npm)

MAL-2026-13063

Immediate action

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

npm uninstall boxy-maker-scroll

What this malware does

[email protected] executes a remote binary dropper the moment the module is loaded. index.js unconditionally requires polyfill.js, which selects a platform-specific endpoint (linux_x64, darwin_arm64, win32, etc.), downloads an opaque native executable from one of three Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS-TXT base64-chunked fallback over *.dl.wel1.ru subdomains, writes the payload to a temp path under a cover-story name (dotnet_diag<hex>.exe on Windows,.cache_<hex> on Unix), chmods it 0755, and spawns it detached via /bin/sh -c '<path> &' on Unix or cmd.exe /c start /b on Windows. Destination hostnames and fallback domains are reconstructed at runtime by.join()-ing split string fragments to defeat plain-text grep. Environment-variable opt-out flags (DISABLE_TELEMETRY and similar) plus a lock file provide plausible-deniability framing, but the package's advertised purpose (a 'boxy maker scroll adapter') has no legitimate need for downloading and executing native binaries from anonymous infrastructure. Installing or requiring this package results in arbitrary attacker-controlled code executing on the installer's machine.

Malicious versions

1 flagged

35.6.7

Indicators of compromise (SHA-256)

a06d379928c2633009c8dc7d89921205689ffb6ed8fa03ba74f67f557836c6f4

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

Campaign

IN-MAL-2026-015315

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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