Which versions of pipmodule823 are malicious?

The following PyPI versions of pipmodule823 are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate pipmodule823 if I installed it?

Remove pipmodule823 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed pipmodule823 — how do I know if it already compromised me?

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

Yes — pipmodule823 is associated with the RLMA-2025-03661, 2025-07-pipmodule83, RLUA-2026-00593 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 pipmodule823 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 pipmodule823 (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pipmodule823 across your stack and pipelines.

Malicious package

pipmodule823PyPI

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

MAL-2025-6564

Immediate action

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

pip uninstall pipmodule823

What this malware does

If run as a module, the package downloads and executes a remote script. At the time of check, the remote script was just opening a popup; thus it's not classified as clearly malicious.

Through the package description related to "cirhenly" package, which was uploaded by "0x92nw" - see campaign 2025-07-0x92nw

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: 2025-07-pipmodule83

Reasons (based on the campaign):

Downloads and executes a remote malicious script.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

c1f07f206c190c756c90730237cd6287bcf0ff08d1626294c13f5386f46ca32c

a1158fdbcf3fc5195cdf4ebab8d8dbbcdc9dc76ecc1423ffd3dd699fd8394b9c

57b078ffca6f219848df2289282933442be06a2932d0d163ede59fe4a533faca

6d2582054e706611dceb4c2d9738b0953657440d6e7e584c78bbb042fcef1334

fa3490f2a31ab11a9d8b1ca9485f679f083c8a738dafe24d38ef0c5048e08fa0

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pipmodule823 (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pipmodule823 across your stack and pipelines.
If you installed it — respond
Remove pipmodule823 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If pipmodule823 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 pipmodule823 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. pipmodule823 on PyPI has been identified as a malicious package (version 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-036612025-07-pipmodule83RLUA-2026-00593

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks pipmodule823-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring