Which versions of story-mcp-hub are malicious?

The following PyPI versions of story-mcp-hub are flagged malicious: 9999.0.0. Treat any of these as compromised.

How do I remediate story-mcp-hub if I installed it?

story-mcp-hub 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 story-mcp-hub — how do I know if it already compromised me?

If story-mcp-hub 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 story-mcp-hub part of a known attack campaign?

Yes — story-mcp-hub is associated with the RLMA-2025-02537, GENERIC-standard-pypi-install-pentest, RLUA-2026-00782 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 story-mcp-hub 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 story-mcp-hub (version 9999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging story-mcp-hub across your stack and pipelines.

Malicious package

story-mcp-hubPyPI

Malicious code in story-mcp-hub (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-3471

Immediate action

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

pip uninstall story-mcp-hub

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

9999.0.0

Indicators of compromise (SHA-256)

7206d81f9c1125962303da3ef99727c560158d0203e81804e2673b008b36bc69

77b5575da35212d2366817e38022c3e4a8d1075eb900ae74d0b8f9aaad3ae59b

e663c654e00b0eb9bdfecb5446b4c56d8f8799ef600619c3f0577bd30863476b

427390115c195d52d389228bd300b322b4f78877545bdcb0e2fefab7ba732cde

8a9b4971d2e559b418de6310ba5dca18b25bdf6c81e395f1ed69260bb3908952

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 story-mcp-hub (version 9999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging story-mcp-hub across your stack and pipelines.
If you installed it — respond
story-mcp-hub 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 story-mcp-hub 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 story-mcp-hub 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. story-mcp-hub on PyPI has been identified as a malicious package (version 9999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-02537GENERIC-standard-pypi-install-pentestRLUA-2026-00782

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks story-mcp-hub-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