Which versions of check-codeowners are malicious?

The following PyPI versions of check-codeowners are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate check-codeowners if I installed it?

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

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

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

Malicious package

check-codeownersPyPI

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

MAL-2024-11556

Immediate action

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

pip uninstall check-codeowners

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

99.99.99

Indicators of compromise (SHA-256)

2891d4044a7c4515368960de533c22c54ae57cb287e4606f546b0cd68fcd4fc8

56b8eb45a4b5e2fd93a1b63cdc0d5b8923accd3b4deb51f0f1893bca87cddc14

946e4f02e3bc9fafb3561655eaaf71128a7a37469e09460b0b9f3f204e850185

f2484ad6104a24cd6557709b189b6f1f07dffadee57fed59e58e76b0e58de172

64cf60bb4eca4078f18d3afd95900fcace0d825b9fa9eaf9c6108e119f44b88a

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

Campaign

RLMA-2024-11002GENERIC-standard-pypi-install-pentestRLUA-2026-00187

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks check-codeowners-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