Which versions of voicemetterr are malicious?

The following PyPI versions of voicemetterr are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5. Treat any of these as compromised.

How do I remediate voicemetterr if I installed it?

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

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

Yes — voicemetterr is associated with the 2025-11-voicemetterr 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 voicemetterr 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 voicemetterr (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging voicemetterr across your stack and pipelines.

Malicious package

voicemetterrPyPI

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

MAL-2025-191921

Immediate action

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

pip uninstall voicemetterr

What this malware does

Package sends image files to a hardcoded Discord webhook. It requires manual start and expects user's interaction.

However, the package clearly impersonate a brand and so tries to hide the real actions.

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

Campaign: 2025-11-voicemetterr

Reasons (based on the campaign):

other
impersonation
files-exfiltration

Malicious versions

6 flagged

1.0.01.0.11.0.21.0.31.0.41.0.5

Indicators of compromise (SHA-256)

0956b9dd420ca821511344815cb51fa22458f39542a1b1524084186a1bcc5401

96387f13bb167829d9ffd47e15174e794c9a0a0922ca411c2b5d67f33725d769

1e1777e750c426898d5c591e80284da1ea3cf1f5e139a6bb1bafe2567c0d01d1

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

Campaign

2025-11-voicemetterr

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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