Which versions of freelabs are malicious?

The following PyPI versions of freelabs are flagged malicious: 1.1.5. Treat any of these as compromised.

How do I remediate freelabs if I installed it?

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

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

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

Search your lockfiles and build artifacts for freelabs (version 1.1.5).

Malicious package

freelabsPyPI

Advisory published May 16, 2025Updated Dec 12, 2025

freelabs is a confirmed malicious PyPI package (MAL-2025-191734) that steals credentials and exfiltrates sensitive data (malicious version 1.1.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in freelabs (PyPI)

MAL-2025-191734

Immediate action

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

pip uninstall freelabs

What this malware does

Once imported, the package scans the disk looking for Telegram Desktop files and exfiltrate them to a hardcoded remote target.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-05-freelabs

Reasons (based on the campaign):

target:telegram
files-exfiltration
obfuscation

Malicious versions

1 flagged

1.1.5

Indicators of compromise (SHA-256)

8d270b59cbf41a6cbe26db37b70cc356a5c81c4f9bee5a30daa76a32d8883778

4807374c9df366a20bb6e33eb5a4c7c8e1790cd10db475eb23c7ffa799c2e7cd

8e4221044e5d8f9b0c8196327ee1512b19f1e3b6b23882b3220dbec95fc04943

Detection & response playbook

Credential / info stealer

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

Campaign

2025-05-freelabs

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database