What does the the-storyverse malware do?

The package the-storyverse was found to contain malicious code. The OpenSSF Package Analysis project identified 'the-storyverse' @ 5.6.9 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of the-storyverse are malicious?

The following npm versions of the-storyverse are flagged malicious: 5.6.9. Treat any of these as compromised.

How do I remediate the-storyverse if I installed it?

Remove the-storyverse 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 the-storyverse — how do I know if it already compromised me?

If the-storyverse was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find the-storyverse across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for the-storyverse (version 5.6.9).

Malicious package

the-storyversenpm

Advisory published Feb 22, 2026Updated Feb 23, 2026

the-storyverse is a confirmed malicious npm package (MAL-2026-980) that executes malicious code on install (malicious version 5.6.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in the-storyverse (npm)

MAL-2026-980

Immediate action

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

npm uninstall the-storyverse

What this malware does

The package the-storyverse was found to contain malicious code.

The OpenSSF Package Analysis project identified 'the-storyverse' @ 5.6.9 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

5.6.9

Indicators of compromise (SHA-256)

09e958d1d3f8084930d29c32902be20c176f89fda711767fe04727009d73a341

2885a4f6fa566cedcd5c365fe4435186a31ed8913af26f8a06bbee3d760e66cb

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for the-storyverse (version 5.6.9).
If you installed it — respond
Remove the-storyverse 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 the-storyverse was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. the-storyverse on npm has been identified as a malicious package (version 5.6.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks the-storyverse-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