Which versions of boxy-story-header are malicious?

The following npm versions of boxy-story-header are flagged malicious: 35.7.2. Treat any of these as compromised.

How do I remediate boxy-story-header if I installed it?

boxy-story-header establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

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

Malicious package

boxy-story-headernpm

boxy-story-header is a confirmed malicious npm package (MAL-2026-13085) that opens a backdoor for remote access (malicious version 35.7.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-story-header (npm)

MAL-2026-13085

Immediate action

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

npm uninstall boxy-story-header

What this malware does

index.js unconditionally requires./setup on load. setup.js reconstructs C2 hostnames by array-joining string fragments (Cloudflare Workers subdomains including oob-worker.cf99-9b3.workers.dev) and falls back to a base64-chunked DNS-TXT covert channel under numeric subdomains of wel1.ru. It downloads a platform-specific binary via https.get, writes it to /tmp/.cache_<hex> or %TEMP%\dotnet_diag_<hex>.exe under a hidden or system-masquerading name, chmods it 0755, and spawns it detached through /bin/sh -c or cmd.exe /c start /b with no signature or hash verification. lib/telemetry.js reimplements the same fetch-decode-chmod-spawn dropper primitives (Buffer.from(...,'base64'), fs['chmod'+'Sync'](path, mode|0o755), cp.spawn('/bin/sh',['-c',filePath+' &'],{detached:true})). Host obfuscation, DNS-TXT fallback, hidden/masquerading filenames, and unauthenticated remote execution on import satisfy the install-time-rce fingerprint (known-bad-infrastructure dropper).

Malicious versions

1 flagged

35.7.2

Indicators of compromise (SHA-256)

6a1273cea6d0d4cdf432c47fda7e95f529858a1bddefaaeeb976248ea55504f2

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-story-header (version 35.7.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-story-header across your stack and pipelines.
If you installed it — respond
boxy-story-header establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If boxy-story-header 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-story-header 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-story-header on npm has been identified as a malicious package (version 35.7.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015286

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database