Which versions of package-346234294 are malicious?

The following PyPI versions of package-346234294 are flagged malicious: 1.0.1, 1.0.2, 1.0.3. Treat any of these as compromised.

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

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

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

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

Malicious package

package-346234294PyPI

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

MAL-2025-191807

Immediate action

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

pip uninstall package-346234294

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

3 flagged

1.0.11.0.21.0.3

Indicators of compromise (SHA-256)

4db08e46dd885feacc30b279cba830889aea1fb2f6e4844ed72a7f9a9a516aa5

c9741d027897445cdd34a40de0f592a42641170b88a9cbab6cee3dbaaeeedb39

fdf1050bb50071b259a5ac2dd73c9baf2254a911def0a6037350ce319c9c7649

12da6501efaf0b9cf42494b5ba6b1841b06d8677a0486b592b7c5c5c1f759808

dc476fc3cae10c61dc1246246ed37f88e10dfa1652fdfe472bde067acb91e68e

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

Campaign

GENERIC-simple-testsRLMA-2026-01686

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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