Which versions of neuralforge-ml are malicious?

The following PyPI versions of neuralforge-ml are flagged malicious: 0.9.9. Treat any of these as compromised.

How do I remediate neuralforge-ml if I installed it?

neuralforge-ml 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 neuralforge-ml — how do I know if it already compromised me?

If neuralforge-ml was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is neuralforge-ml part of a known attack campaign?

Yes — neuralforge-ml is associated with the 2026-05-neuralforge-ml 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 neuralforge-ml across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for neuralforge-ml (version 0.9.9).

Malicious package

neuralforge-mlPyPI

Advisory published May 30, 2026Updated May 30, 2026

neuralforge-ml is a confirmed malicious PyPI package (MAL-2026-5090) that steals credentials and exfiltrates sensitive data (malicious version 0.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in neuralforge-ml (PyPI)

MAL-2026-5090

Immediate action

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

pip uninstall neuralforge-ml

What this malware does

The package contains stub code only imitating real actions. Starting with version 0.9.9, the code contains exfiltration capability activated under specific conditions.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-05-neuralforge-ml

Reasons (based on the campaign):

exfiltration-env-variables
obfuscation

Malicious versions

1 flagged

0.9.9

Indicators of compromise (SHA-256)

c0a68c3ef2f7680eab753f62cc1792ae7df68bb15400e09971cc9c34a444307b

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for neuralforge-ml (version 0.9.9).
If you installed it — respond
neuralforge-ml 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 neuralforge-ml was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. neuralforge-ml on PyPI has been identified as a malicious package (version 0.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-05-neuralforge-ml

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks neuralforge-ml-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

Explore

All malware advisories How O3 detects malware Vulnerability database