boxy-page-storynpm
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-page-story (version 35.8.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-page-story across your stack and pipelines.
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.
Did it already run?
If boxy-page-story 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-page-story 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
Campaign
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.