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

heft-storybook-v6-react-tutorial-storykitnpm

heft-storybook-v6-react-tutorial-storykit is a confirmed malicious npm package (MAL-2026-14083) that executes malicious code on install (malicious versions 1000.0.13, 1000.0.16). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in heft-storybook-v6-react-tutorial-storykit (npm)

MAL-2026-14083
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall heft-storybook-v6-react-tutorial-storykit

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged
1000.0.131000.0.16

Indicators of compromise (SHA-256)

fb5955868f72344703128add3301e3a85b51773de502f24e636fe0b9bba86d42
9151be4f8cd6deecfaec8ac46329e6a2b744c53db589872b79c60f9f973477da
982cec09128ffa9a1214165cf24b0b0b6ead5950130ec459fd3592e68e6764b2

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 heft-storybook-v6-react-tutorial-storykit (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging heft-storybook-v6-react-tutorial-storykit across your stack and pipelines.

  2. If you installed it — respond

    Remove heft-storybook-v6-react-tutorial-storykit 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 heft-storybook-v6-react-tutorial-storykit 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 heft-storybook-v6-react-tutorial-storykit 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. heft-storybook-v6-react-tutorial-storykit on npm has been identified as a malicious package (versions 1000.0.13, 1000.0.16 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-p9w8-w4px-249vRLMA-2026-06268RLUA-2026-10746

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks heft-storybook-v6-react-tutorial-storykit-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.

Explore

heft-storybook-v6-react-tutorial-storykit (npm) malicious package — MAL-2026-14083 | O3 Security