Which versions of neurodrift are malicious?

The following PyPI versions of neurodrift are flagged malicious: 1.21. Treat any of these as compromised.

How do I remediate neurodrift if I installed it?

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

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

Yes — neurodrift is associated with the 2026-06-easyaillm 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 neurodrift 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 neurodrift (version 1.21). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging neurodrift across your stack and pipelines.

Malicious package

neurodriftPyPI

Malicious code in neurodrift (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-5797

Immediate action

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

pip uninstall neurodrift

What this malware does

During installation, the code attempts to download and start a malicious executable.

Likely related to 2025-08-raknet-testing-package.

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

Campaign: 2026-06-easyaillm

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation
malware
tool:mshta

Malicious versions

1 flagged

1.21

Indicators of compromise (SHA-256)

8ac6b3dafe24c6df163af1e917f75bb49a8b2ae1ecb1baa4f7914922c8d5ad83

4bbebf2d437cf04868e7e78e34fd21cc658acdd55614cc902e1d577f2a335ae6

49b90734cf162bc3013cf1325a8b118994751cc9bf0f6fa159d7fcf0d54c4189

1b632fa784b6125daaba0e4a2b9e775bc4fec21c7d41127b887f9dfe6e873ce0

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

Campaign

2026-06-easyaillm

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks neurodrift-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