Which versions of wayspiritmcp-enconly are malicious?

The following PyPI versions of wayspiritmcp-enconly are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3. Treat any of these as compromised.

How do I remediate wayspiritmcp-enconly if I installed it?

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

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

Yes — wayspiritmcp-enconly is associated with the 2025-11-wayspirit 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 wayspiritmcp-enconly 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 wayspiritmcp-enconly (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wayspiritmcp-enconly across your stack and pipelines.

Malicious package

wayspiritmcp-enconlyPyPI

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

MAL-2025-191924

Immediate action

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

pip uninstall wayspiritmcp-enconly

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

4 flagged

0.1.00.1.10.1.20.1.3

Indicators of compromise (SHA-256)

d0ef12f9aacc06b350c0b277ad3fe29beb77c94eb15eef2fe4a1b85751d1dd53

b075eb7116e55dd48db0e026ce51a42ec4e7e1e100b4b68c8a42d4b35411f749

ff9fe34e29d83ea07b609b8b2ce3002137f28c2d7ddbe53600af42dc71bb0cec

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

Campaign

2025-11-wayspirit

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks wayspiritmcp-enconly-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