Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

boxy-storybook-addon-changelognpm

boxy-storybook-addon-changelog is a confirmed malicious npm package (MAL-2026-13086) that executes malicious code on install (malicious version 35.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-storybook-addon-changelog (npm)

MAL-2026-13086
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall boxy-storybook-addon-changelog

What this malware does

On require of the package, index.js loads ext.js which downloads an opaque platform-specific binary from one of four hardcoded Cloudflare Workers hosts (oob-worker.cf*.workers.dev), with a DNS-TXT chunked base64 fallback via *.dl.wel1.ru resolvers. Hostnames are reassembled at runtime via Array.join to evade static inspection. The fetched payload is written to /var/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod 0755'd, and spawned detached via /bin/sh -c "<path> &" or cmd.exe /c start /b, then unref()'d. A second module lib/telemetry.js bundles the same dropper primitives (child_process spawn, fs.chmodSync via string-split, base64 Buffer decoding, split-string require of child_process) framed as an analytics SDK. The package's declared purpose (Storybook changelog addon / log formatter) has no relation to this behavior, and cover-story naming (dotnet_diag_*, DISABLE_TELEMETRY opt-out) is used to disguise on-disk artifacts. Package name resembles legitimate Storybook addons.

Malicious versions

1 flagged
35.1.2

Indicators of compromise (SHA-256)

0ec351f143fde732be84b60d329ba254cda918df3ebb25882371a8c5d96a3dd0

Detection & response playbook

Malicious package

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-storybook-addon-changelog (version 35.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-storybook-addon-changelog across your stack and pipelines.

  2. If you installed it — respond

    Remove boxy-storybook-addon-changelog 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.

  3. Did it already run?

    If boxy-storybook-addon-changelog 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.

  4. How O3 protects you

    O3 blocks boxy-storybook-addon-changelog 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-storybook-addon-changelog on npm has been identified as a malicious package (version 35.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015287

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks boxy-storybook-addon-changelog-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
boxy-storybook-addon-changelog (npm) malicious package — MAL-2026-13086 | O3 Security