Which versions of j5gnpfweguiwerbngpiutbgn0iutb0pfwef are malicious?

The following PyPI versions of j5gnpfweguiwerbngpiutbgn0iutb0pfwef are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate j5gnpfweguiwerbngpiutbgn0iutb0pfwef if I installed it?

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

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

Yes — j5gnpfweguiwerbngpiutbgn0iutb0pfwef is associated with the RLMA-2024-11071, 2024-10-lokopoil23, RLUA-2026-00435 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 j5gnpfweguiwerbngpiutbgn0iutb0pfwef 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 j5gnpfweguiwerbngpiutbgn0iutb0pfwef (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging j5gnpfweguiwerbngpiutbgn0iutb0pfwef across your stack and pipelines.

Malicious package

j5gnpfweguiwerbngpiutbgn0iutb0pfwefPyPI

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

MAL-2024-11617

Immediate action

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

pip uninstall j5gnpfweguiwerbngpiutbgn0iutb0pfwef

What this malware does

According to the description, packages should demonstrate the dependency confusion attack. The realisation is, in fact, a spamming with packages having as the only purpose reporting basic data like hostname and current working directory.

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: 2024-10-lokopoil23

Reasons (based on the campaign):

dependency-confusion

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c8152984fa926b95e0c695de87fa6ec16390bdaeadd8df53a06d1017d9bbb528

3ed45b2e73cf483443614d864347dd861533edc8529747c7f7b02fa611d208e9

f32453dbd5b2857fbf4766d0c1573b109be79c0013d276ecdfce38105c4580f9

04820ff0904df5e71c821215b1b4e60afb6587e33292d74e7f06b6c6312a8ad9

1dac432f87a118fe12e90516a31ec85277e8e7ea19c11fb3b0f897a5d9cbe997

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

Campaign

RLMA-2024-110712024-10-lokopoil23RLUA-2026-00435

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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