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

wayspiritmcp-weatherPyPI

Malicious code in wayspiritmcp-weather (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191927
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall wayspiritmcp-weather

What this malware does

Package seems to provide an MCP server, but in fact contains attempts to make an LLM agent break safeguards. As the request is about leaves just a flag, it seems to be research.

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: 2025-11-wayspirit

Reasons (based on the campaign):

  • llm-threat

Malicious versions

56 flagged
0.1.00.1.10.1.20.1.30.1.40.1.50.1.60.1.70.1.80.1.90.1.100.1.110.2.10.2.20.2.30.2.40.2.50.2.60.2.70.2.80.2.90.3.00.3.10.3.20.3.30.3.40.4.00.4.10.4.20.4.30.4.40.4.50.4.60.5.00.5.10.6.00.6.10.6.20.6.30.7.00.7.10.7.20.7.30.7.40.7.50.7.60.7.70.7.80.7.90.7.100.7.110.7.120.7.130.7.140.7.150.8.0

Indicators of compromise (SHA-256)

1912a9f32d32b7620d986ec2a9fe13bef75616ae7f641319121559ac59c02241
c3dbe830c7b2364daef2e4634c16062b86b0b26b88f95533e9413aa91bc646fd
964f7b61870df92413da3344a6c03271c4f1cb91fe8159d0ce0b87dd2e9a7361
d8974676d46d2859c016fc49b2f45c393073cfae7d1698aa80762f0e25db1f11

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 wayspiritmcp-weather (56 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wayspiritmcp-weather across your stack and pipelines.

  2. If you installed it — respond

    Remove wayspiritmcp-weather 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 wayspiritmcp-weather 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 wayspiritmcp-weather 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. wayspiritmcp-weather on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7, and 48 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-11-wayspirit

References

Credits

  • Kamil Mańkowski (kam193)

Detect & block this

O3 blocks wayspiritmcp-weather-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.

wayspiritmcp-weather (PyPI) malicious package — MAL-2025-191927 | O3 Security