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 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 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for freelabs (version 1.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging freelabs across your stack and pipelines.

Malicious package

freelabsPyPI

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

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for freelabs (version 1.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging freelabs across your stack and pipelines.
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 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 freelabs 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. 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