Which versions of easyreg are malicious?

The following PyPI versions of easyreg are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate easyreg if I installed it?

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

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

Yes — easyreg is associated with the 2026-02-pywin-simple-gui 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 easyreg across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for easyreg (version 1.0.0).

Malicious package

easyregPyPI

Advisory published Feb 17, 2026Updated Feb 18, 2026

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

Malicious code in easyreg (PyPI)

MAL-2026-932

Immediate action

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

pip uninstall easyreg

What this malware does

The package pretends to be a development helper but, in fact, downloads a remote executable. Dynamic analysis reveals actions like disabling Windows Defender and interest in cryptocurrencies as well as using Telegram as C2.

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

Campaign: 2026-02-pywin-simple-gui

Reasons (based on the campaign):

impersonation
Downloads and executes a remote executable.
modify-system-without-consent
crypto-related

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2897582bf6c0c29d4fc679ee338263019a8a5d5bcb66b5ae2c59454d6c967d6a

1d44104a6037026075ea91a49dc8ea7d6aaec85afe0584e834dc87e3df97f183

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for easyreg (version 1.0.0).
If you installed it — respond
easyreg 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 easyreg 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. easyreg on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-02-pywin-simple-gui

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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