Which versions of package-346234293 are malicious?

The following PyPI versions of package-346234293 are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate package-346234293 if I installed it?

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

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

Yes — package-346234293 is associated with the RLMA-2025-02516, GENERIC-simple-tests, RLUA-2026-00579 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 package-346234293 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 package-346234293 (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging package-346234293 across your stack and pipelines.

Malicious package

package-346234293PyPI

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

MAL-2025-3453

Immediate action

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

pip uninstall package-346234293

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

91d1f040f412c6b02fd4ed3f1b8454a688e674fc1b55679a1bbac09c31bf21d5

4a9dc989022aa9c3a0e8afb13b36c95c5dbcabedc611b7bd0f9756fdd576c5d9

9a3e0b5450d5b6de8efa950815a198f42f31514206305057d1ec10e308875244

0bcfb555a154c13b7b07d0fdb1af540abe958de22c06092d51eca778c20a5f4d

99fc7b2dd144757c6d5ac1c1cb7ba684325af82c5e28c0644b1e3397747ba375

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

Campaign

RLMA-2025-02516GENERIC-simple-testsRLUA-2026-00579

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks package-346234293-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