Which versions of boxy-lcd are malicious?

The following npm versions of boxy-lcd are flagged malicious: 35.2.3. Treat any of these as compromised.

How do I remediate boxy-lcd if I installed it?

boxy-lcd is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

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

Malicious package

boxy-lcdnpm

boxy-lcd is a confirmed malicious npm package (MAL-2026-13052) that steals credentials and exfiltrates sensitive data (malicious version 35.2.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-lcd (npm)

MAL-2026-13052

Immediate action

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

npm uninstall boxy-lcd

What this malware does

The package's index.js top-level requires setup.js, which on load fetches an OS-specific executable from string-concat-obfuscated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev) and additional hosts under dl.wel1.ru (sdk./ext./pkg./net.), with a DNS-TXT base64 fallback channel. The fetched bytes are written to a hidden temp path with masquerading names such as.cache_<hex> and dotnet_diag_<hex>.exe, chmod 0755, and spawned detached via /bin/sh or cmd. Network destinations and the child_process require string are assembled at runtime from split literals to evade static analysis; the exported BoxyLcd class is a non-functional stub, and opt-out env vars are named to resemble legitimate telemetry (analytics_state, DISABLE_TELEMETRY). Any consumer that installs or requires boxy-lcd triggers download-and-execute of an opaque, author-controlled binary on the installer's host.

Malicious versions

1 flagged

35.2.3

Indicators of compromise (SHA-256)

85c7174f43951c87b6b7ffb67430170a9b655978a1fe64654729c87fe35ced60

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-lcd (version 35.2.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-lcd across your stack and pipelines.
If you installed it — respond
boxy-lcd is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If boxy-lcd 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-lcd 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-lcd on npm has been identified as a malicious package (version 35.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015329

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-lcd-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database