NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

boxy-page-storynpm

Advisory published Updated

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

Malicious code in boxy-page-story (npm)

MAL-2026-13074
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall boxy-page-story

What this malware does

On require, index.js loads./runtime, which reconstructs C2 hostnames from string-array concatenation to hide four oob-worker.cf1{00,01,02,03}-*.workers.dev endpoints and a wel1.ru DNS-TXT covert-channel fallback (chunk-count TXT at c.<domain>, base64 chunks at <n>.<domain>, reassembled and base64-decoded). A platform-specific binary is downloaded, written to /tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755'd, and spawned detached via /bin/sh -c "<path> &" or cmd.exe /c start /b. No hash or signature verification; hosts are attacker-controlled non-publisher infrastructure. Fetch is gated by absence of a recent cache file and DO_NOT_TRACK-style env vars. index.js wraps the require in try/catch to swallow errors silently.

Malicious versions

1 flagged
35.8.5

Indicators of compromise (SHA-256)

6cb3184221c24b500fca09d9e96c886b1ffe703d60b121150180b2387a87c48d

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for boxy-page-story (version 35.8.5).

  2. If you installed it — respond

    boxy-page-story 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.

  3. Did it already run?

    If boxy-page-story was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. boxy-page-story on npm has been identified as a malicious package (version 35.8.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015308

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

boxy-page-story (npm) malicious package — MAL-2026-13074 | O3 Security