Which versions of krisp-audio are malicious?

The following PyPI versions of krisp-audio are flagged malicious: 0.0.0, 1.0.0. Treat any of these as compromised.

How do I remediate krisp-audio if I installed it?

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

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

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

Malicious package

krisp-audioPyPI

Malicious code in krisp-audio (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191643

Immediate action

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

pip uninstall krisp-audio

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

2 flagged

0.0.01.0.0

Indicators of compromise (SHA-256)

645738abfcbd7a8e67f921ccc133aaf306bea38832f8effd55a379570aac8889

d0951a25e0000fc6bec3b366f80c003b6ee300acf67acfdedb4c6cc99db069cf

1940a2f9c0907fd633cc07fcc96fad89f2e4c55cbd38d5fe8df09d1c4048c906

e006d5a3b7d18be847d5708c763d2c2ef0dd97f43b74bbfe2b040ad0fc8df7d1

b88a36f67339ba5726ac683bafac242a18d2d91fd99d64e4ec494f6d8419867a

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

Campaign

RLMA-2025-05614GENERIC-standard-pypi-install-pentestRLUA-2026-00460

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks krisp-audio-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