Which versions of neutrl-contracts are malicious?

The following PyPI versions of neutrl-contracts are flagged malicious: 2.0.0, 2.0.1, 2.0.2. Treat any of these as compromised.

How do I remediate neutrl-contracts if I installed it?

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

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

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

Malicious package

neutrl-contractsPyPI

neutrl-contracts is a confirmed malicious PyPI package (MAL-2026-13709) that steals credentials and exfiltrates sensitive data (malicious versions 2.0.0, 2.0.1, 2.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in neutrl-contracts (PyPI)

MAL-2026-13709

Immediate action

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

pip uninstall neutrl-contracts

What this malware does

This package intentionally depends on a malicious package.

This campaign exfiltrates sensitive environment variables, SSH keys, dotenv files and other credentials. The malicious code is hidden in a dependency package (e.g. neutrl-core) in a function disguised as telemetry, and requires activates once the attacker-controlled endpoint delivers the command. While the user can provide their blockchain endpoints, the code makes sure the malicious endpoint is always included in the configuration. In analyzed versions, the dependent packages did not use the malicious code but were clearly prepared for the supply chain attack.

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

Campaign: 2026-08-neutrl-core

Reasons (based on the campaign):

files-exfiltration
exfiltration-env-variables
exfiltration-ssh-keys
crypto-related
action-hidden-in-lib-usage
The malicious code is intentionally included in a dependency of the package
exfiltration-crypto
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
exfiltration-credentials

Malicious versions

3 flagged

2.0.02.0.12.0.2

Indicators of compromise (SHA-256)

f0a6030f2cc65968de85749a2fafe2380bbb44fdc7db473763c5a82af5d79bc4

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

Campaign

2026-08-neutrl-core

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks neutrl-contracts-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