Which versions of chosenrce18 are malicious?

The following PyPI versions of chosenrce18 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate chosenrce18 if I installed it?

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

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

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

Malicious package

chosenrce18PyPI

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

MAL-2025-4210

Immediate action

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

pip uninstall chosenrce18

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.0.0

Indicators of compromise (SHA-256)

5997b6b0806140b74c5c1c74d5d6a4ead40b1012e764916248b50efd1fa90e1c

da13fc209516afa1165fe7aeebde261609d94561675c922cd1eb65132400c753

254a6f89fa4e8c08d6ac8622c13f3aa2e4213b57587fa14db03b51e32e406f96

0e10314f82261da2382030092a7cb9134297d212b95bea3bc356825ef38e1f6a

ebc0d422ccc5b48a2ad56d13e8f505d159c22c65ef0733d18623c82207cfc19f

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

Campaign

RLMA-2025-02562GENERIC-standard-pypi-install-pentestRLUA-2026-00191

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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