Which versions of @caspianph/storyteller are malicious?

The following npm versions of @caspianph/storyteller are flagged malicious: 1.1.13. Treat any of these as compromised.

How do I remediate @caspianph/storyteller if I installed it?

@caspianph/storyteller is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @caspianph/storyteller — how do I know if it already compromised me?

If @caspianph/storyteller 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 @caspianph/storyteller part of a known attack campaign?

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

Malicious package

@caspianph/storytellernpm

Malicious code in @caspianph/storyteller (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6120

Immediate action

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

npm uninstall @caspianph/storyteller

What this malware does

The package ships setup.cjs containing heavily obfuscated JavaScript with hex-mangled identifiers (_0x32549a, _0x4b2b44, _0x78c349, _0x119ac2) typical of payload-hiding techniques. A file named setup.cjs in an npm package is structurally positioned to be invoked from a lifecycle hook (preinstall/install/postinstall) or required at module load. Legitimate npm packages do not obfuscate their install-time code; obfuscation in this position is overwhelmingly used to hide network beacons, credential reads, or dropper logic from casual inspection.

Malicious versions

1 flagged

1.1.13

Indicators of compromise (SHA-256)

3bd24daaa395f2e6bfae7c6e6f488a6e114b87e2606ec1bce7dcd4ab6a92f40a

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @caspianph/storyteller (version 1.1.13). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @caspianph/storyteller across your stack and pipelines.
If you installed it — respond
@caspianph/storyteller is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @caspianph/storyteller 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 @caspianph/storyteller 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. @caspianph/storyteller on npm has been identified as a malicious package (version 1.1.13 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006986

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @caspianph/storyteller-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring