What does the liblapack-dev malware do?

The OpenSSF Package Analysis project identified 'liblapack-dev' @ 0.0.1 (pypi) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Which versions of liblapack-dev are malicious?

The following PyPI versions of liblapack-dev are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate liblapack-dev if I installed it?

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

If liblapack-dev 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.

How do I find liblapack-dev across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for liblapack-dev (version 0.0.1).

Malicious package

liblapack-devPyPI

liblapack-dev is a confirmed malicious PyPI package (MAL-2023-8306) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in liblapack-dev (PyPI)

MAL-2023-8306

Immediate action

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

pip uninstall liblapack-dev

What this malware does

The OpenSSF Package Analysis project identified 'liblapack-dev' @ 0.0.1 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

01a9f7fec70ee10cd7862c22e2c8257811997655e86e342b7bf61d0bd2b95154

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for liblapack-dev (version 0.0.1).
If you installed it — respond
Remove liblapack-dev 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 liblapack-dev 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. liblapack-dev on PyPI has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks liblapack-dev-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