Which versions of unreal-mladapter are malicious?

The following PyPI versions of unreal-mladapter are flagged malicious: 99999.0.0. Treat any of these as compromised.

How do I remediate unreal-mladapter if I installed it?

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

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

Yes — unreal-mladapter is associated with the GENERIC-standard-pypi-install-pentest, IN-MAL-2026-008125 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 unreal-mladapter 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 unreal-mladapter (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 unreal-mladapter across your stack and pipelines.

Malicious package

unreal-mladapterPyPI

Malicious code in unreal-mladapter (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-6736

Immediate action

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

pip uninstall unreal-mladapter

What this malware does

The package name unreal-mladapter mimics Epic Games' internal UnrealMLAdapter plugin and is published at version 99999.0.0 — the canonical high-version bump used in dependency-confusion attacks to override private/internal resolution. On any import unreal_mladapter, the top-level init.py spawns a background thread that POSTs a JSON payload containing the installer's hostname, USER/USERNAME environment variable, and current working directory to http://109.123.247.172/pypi over plaintext HTTP. Errors are swallowed. Package metadata is placeholder (author 'Security Research', description 'Internal package'). The import-time exfiltration of host identifiers to a hardcoded non-publisher bare-IP endpoint, combined with the 99999.0.0 dependency-confusion version and internal-namespace impersonation, is an unambiguous supply-chain attack shape.

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)

b8b4f17043a9c57ea2087c59c771151186c117ab64cbf5c45df85df62469aa89

126bf3493d123333b47fba2ed68e30c085c8266dfb4d16923a81e9ee094f4780

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 unreal-mladapter (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 unreal-mladapter across your stack and pipelines.
If you installed it — respond
unreal-mladapter 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 unreal-mladapter 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 unreal-mladapter 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. unreal-mladapter 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-008125

References

Credits

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

Detect & block this

O3 blocks unreal-mladapter-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