Which versions of qassabi are malicious?

The following PyPI versions of qassabi are flagged malicious: 1.1.8. Treat any of these as compromised.

How do I remediate qassabi if I installed it?

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

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

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

Malicious package

qassabiPyPI

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

MAL-2025-964

Immediate action

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

pip uninstall qassabi

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

1 flagged

1.1.8

Indicators of compromise (SHA-256)

4c93f3a3a4e28974cf4aa3f18d96c9fe7ab1ddf905e942dac265b14faa552d47

ce03a0580ac14adfacce7c7ce51d82d7f730e87456b42c239bf75b4c2f723b33

3ed5e109142f6f718ce92b9e9e8e549ef2182b601cad597a729aae045d182a46

e5c0d3185e0387659979dcd370c7e8eabebe73d1daba2bb645c1c1939187a6b5

a070b7befab884cff5a7dcb4d373c7a2d753597b5a48aab1a947fb0a8fd0c8fb

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

Campaign

RLMA-2025-00505GENERIC-standard-pypi-install-pentestRLUA-2026-00676

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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