Which versions of libgomp are malicious?

The following PyPI versions of libgomp are flagged malicious: 0.1.0, 0.1.1, 1.1.1, 1.1.3, 1.1.4, 1.1.5. Treat any of these as compromised.

How do I remediate libgomp if I installed it?

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

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

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

Malicious package

libgompPyPI

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

MAL-2025-47783

Immediate action

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

pip uninstall libgomp

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

6 flagged

0.1.00.1.11.1.11.1.31.1.41.1.5

Indicators of compromise (SHA-256)

a04a7bf3af246166e32706168ac0b14ebb910542276af35960ce19cb47a38b97

7c596b6492ba6e5554a1b845535bdb72716d5e6a74139e604e99dac9a6175d44

d390b58898a977fec39e6d1fe725cf5c2bcb09b2ecf4c2294a23d75a56dd71a6

787dd2cc589d392ad419ce5499106f31bae5feff25b3f28b74ff58c3483aa69a

10c6431195eb95244f09fc4c0e98ea847131b2b071cd036b62ab41b89f8e5aae

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

Campaign

RLMA-2025-04788GENERIC-standard-pypi-install-pentestRLUA-2026-00468

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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