Which versions of wei516-enconly are malicious?

The following PyPI versions of wei516-enconly are flagged malicious: 0.1.5, 0.1.6, 0.1.7, 0.1.8, 0.1.9, 0.2.0, 0.2.1, 0.2.2, 0.2.3. Treat any of these as compromised.

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

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

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

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

Malicious package

wei516-enconlyPyPI

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

MAL-2025-191929

Immediate action

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

pip uninstall wei516-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

9 flagged

0.1.50.1.60.1.70.1.80.1.90.2.00.2.10.2.20.2.3

Indicators of compromise (SHA-256)

b6497d28bf974ab66f71e15bd20d92b605ddc18d13a8ada88c92153004cff63a

3e40931688b41ac8340ab8f27604ba32f1ea6e364df1e614343cbc4cf0df50e8

7fbddcce3c8145ac83155286283a81984361d1efb324c6307a38d18d547e74c1

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 wei516-enconly (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wei516-enconly across your stack and pipelines.
If you installed it — respond
Remove wei516-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 wei516-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 wei516-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. wei516-enconly on PyPI has been identified as a malicious package (versions 0.1.5, 0.1.6, 0.1.7, 0.1.8, 0.1.9, 0.2.0, 0.2.1, 0.2.2, and 1 more 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 wei516-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