Which versions of j5gnpfweguiwerbngpiutbgn0iutb0pfwfef are malicious?

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

How do I remediate j5gnpfweguiwerbngpiutbgn0iutb0pfwfef if I installed it?

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

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

Yes — j5gnpfweguiwerbngpiutbgn0iutb0pfwfef is associated with the RLMA-2024-11072, 2024-10-lokopoil23, RLUA-2026-00436 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 j5gnpfweguiwerbngpiutbgn0iutb0pfwfef 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 j5gnpfweguiwerbngpiutbgn0iutb0pfwfef (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 j5gnpfweguiwerbngpiutbgn0iutb0pfwfef across your stack and pipelines.

Malicious package

j5gnpfweguiwerbngpiutbgn0iutb0pfwfefPyPI

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

MAL-2024-11618

Immediate action

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

pip uninstall j5gnpfweguiwerbngpiutbgn0iutb0pfwfef

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)

d611549633d8d168b74cc6ebb46afa2a64d6c1c77b884f593420a785d734e7fa

77243cbc9cd8223e444a80c02ae26990b9545c66ddb3bd2213b92ac55abb07ea

41b992b1717ae4c37710bfcb4b86d013ca8f3eb95dc9e06f47bdd813010db976

8d45f3513f69411305b7be7bfbfcd62b62a68655c76bdde942f88f72064c1ac6

6db92150ca96d10a15ca56d129fa6490d3f7f4c279827f0386edd5764a76a070

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 j5gnpfweguiwerbngpiutbgn0iutb0pfwfef (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 j5gnpfweguiwerbngpiutbgn0iutb0pfwfef across your stack and pipelines.
If you installed it — respond
Remove j5gnpfweguiwerbngpiutbgn0iutb0pfwfef 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 j5gnpfweguiwerbngpiutbgn0iutb0pfwfef 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 j5gnpfweguiwerbngpiutbgn0iutb0pfwfef 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. j5gnpfweguiwerbngpiutbgn0iutb0pfwfef 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-110722024-10-lokopoil23RLUA-2026-00436

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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