Which versions of ue-python-tools are malicious?

The following PyPI versions of ue-python-tools are flagged malicious: 99999.0.0. Treat any of these as compromised.

How do I remediate ue-python-tools if I installed it?

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

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

Yes — ue-python-tools is associated with the GENERIC-standard-pypi-install-pentest, IN-MAL-2026-008129 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 ue-python-tools 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 ue-python-tools (version 99999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ue-python-tools across your stack and pipelines.

Malicious package

ue-python-toolsPyPI

Malicious code in ue-python-tools (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-6735

Immediate action

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

pip uninstall ue-python-tools

What this malware does

On import ue_python_tools, the package spawns a background thread that issues an HTTP POST to http://109.123.247.172/pypi carrying a JSON payload composed of the installer's hostname (socket.gethostname()), user identity (os.environ USER/USERNAME), and current working directory (os.getcwd()). The destination is a hardcoded plaintext bare-IP endpoint with no user consent, no configuration surface, and no documented purpose. The package metadata compounds the risk: it is published as version 99999.0.0 with placeholder author 'Security Research' and summary 'Internal package', a version-squat shape designed to be resolved as the 'latest' release by dependency resolvers and to shadow an internal package name via dependency confusion. Installing or importing this package causes installer host identifiers to be transmitted off-machine to an attacker-controlled endpoint.

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

99999.0.0

Indicators of compromise (SHA-256)

9494382fb3885f95987ec830f096aac6cde589cac9485b6a347bafed9a8a7e39

66a6d9d874ce102a9ac674f8f713472a473007dc3d51adb869c5198afc708751

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

Campaign

GENERIC-standard-pypi-install-pentestIN-MAL-2026-008129

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks ue-python-tools-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