Which versions of ptxcompiler are malicious?

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

How do I remediate ptxcompiler if I installed it?

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

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

Yes — ptxcompiler is associated with the RLMA-2025-05627, GENERIC-standard-pypi-install-pentest, RLUA-2026-00614 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 ptxcompiler 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 ptxcompiler (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ptxcompiler across your stack and pipelines.

Malicious package

ptxcompilerPyPI

Malicious code in ptxcompiler (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191653

Immediate action

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

pip uninstall ptxcompiler

What this malware does

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

2 flagged

0.0.01.0.0

Indicators of compromise (SHA-256)

6fb09c12b606b89fa81f470dbafc45bd7f34911703a249749201f5592b14513d

fb5c12f1ed4ca2fcf145bd4049f95230aae78757b49e83998e5d4231b0a5017d

a157c2b8ad78e45eea0b8e20ef6d466cdefbd686ac62041c13580048283ba7a1

f50578824cb0ffc1ec403c3c7492f20f8dfb922b6beabe21362fbbd8c0ad69bb

b0f78fd5d03fddc46ccbdf8789c78ba31f4e2692cdb9b0393775ea871472dc78

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

Campaign

RLMA-2025-05627GENERIC-standard-pypi-install-pentestRLUA-2026-00614

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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