Which versions of pkproxy are malicious?

The following PyPI versions of pkproxy are flagged malicious: 6.9.2. Treat any of these as compromised.

How do I remediate pkproxy if I installed it?

Remove pkproxy from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed pkproxy — how do I know if it already compromised me?

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

Yes — pkproxy is associated with the RLMA-2025-04213 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 pkproxy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pkproxy (version 6.9.2).

Malicious package

pkproxyPyPI

pkproxy is a confirmed malicious PyPI package (MAL-2025-41718) that executes malicious code on install (malicious version 6.9.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pkproxy (PyPI)

MAL-2025-41718

Immediate action

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

pip uninstall pkproxy

Malicious versions

1 flagged

6.9.2

Indicators of compromise (SHA-256)

fac8787f9a2e930a89e504cd938c01b4ff0160bab2a42c04d04d2821135281d9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pkproxy (version 6.9.2).
If you installed it — respond
Remove pkproxy from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If pkproxy 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. pkproxy on PyPI has been identified as a malicious package (version 6.9.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04213

Credits

ReversingLabs · finder

Detect & block this

O3 blocks pkproxy-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database