Which versions of o3-storybook are malicious?

The following npm versions of o3-storybook are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate o3-storybook if I installed it?

Remove o3-storybook 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.

I already installed o3-storybook — how do I know if it already compromised me?

If o3-storybook 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 o3-storybook part of a known attack campaign?

Yes — o3-storybook is associated with the GHSA-vfvv-jmhj-pff4, RLMA-2025-05897 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 o3-storybook 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 o3-storybook (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging o3-storybook across your stack and pipelines.

Malicious package

o3-storybooknpm

o3-storybook is a confirmed malicious npm package (MAL-2025-48748) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in o3-storybook (npm)

MAL-2025-48748

Immediate action

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

npm uninstall o3-storybook

What this malware does

The package communicates with a domain associated with malicious activity.

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

de89e5dde2144657ab48e71c00e9630b08d5d29e6a86daf29f7ce46d3380b18a

05054b26201d9ee30b763a7e12c2f08181ee22b6254f12599fef8599196a6f24

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for o3-storybook (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging o3-storybook across your stack and pipelines.
If you installed it — respond
Remove o3-storybook 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.
Did it already run?
If o3-storybook 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 o3-storybook 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. o3-storybook on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vfvv-jmhj-pff4RLMA-2025-05897

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks o3-storybook-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