Which versions of libavcodec-extra are malicious?

The following PyPI versions of libavcodec-extra are flagged malicious: 99.99.9. Treat any of these as compromised.

How do I remediate libavcodec-extra if I installed it?

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

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

Yes — libavcodec-extra is associated with the GENERIC-hackerone-bugbounty 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 libavcodec-extra 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 libavcodec-extra (version 99.99.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging libavcodec-extra across your stack and pipelines.

Malicious package

libavcodec-extraPyPI

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

MAL-2026-1933

Immediate action

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

pip uninstall libavcodec-extra

What this malware does

During installation or import, the package exfiltrates basic information in a dependency confusion attempt. The user identifies themselves as a HackerOne user abusing the PyPI for the purpose of a bug bounty program.

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-hackerone-bugbounty

Reasons (based on the campaign):

dependency-confusion
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

1 flagged

99.99.9

Indicators of compromise (SHA-256)

00a68b4208fb4614b815e8a867c2155a8667b424e6457e3b72da362edbad9615

837926ebe1825b77add1437c069e04cc67f552a18f79c427d8c786c493f9a312

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

Campaign

GENERIC-hackerone-bugbounty

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks libavcodec-extra-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