Which versions of j5gnpfweguiwerbngpiutbgn0iutb0pfwbdfsfef are malicious?

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

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

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

Yes — j5gnpfweguiwerbngpiutbgn0iutb0pfwbdfsfef is associated with the 2024-10-lokopoil23 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 j5gnpfweguiwerbngpiutbgn0iutb0pfwbdfsfef 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 j5gnpfweguiwerbngpiutbgn0iutb0pfwbdfsfef (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 j5gnpfweguiwerbngpiutbgn0iutb0pfwbdfsfef across your stack and pipelines.

Malicious package

j5gnpfweguiwerbngpiutbgn0iutb0pfwbdfsfefPyPI

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

MAL-2024-9409

Immediate action

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

pip uninstall j5gnpfweguiwerbngpiutbgn0iutb0pfwbdfsfef

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

The OpenSSF Package Analysis project identified 'j5gnpfweguiwerbngpiutbgn0iutb0pfwbdfsfef' @ 0.0.1 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8c86ce5153d87458c534613605bc7080b88c28ebf2ea30c12fe8c576f28624c3

ac082d40cb76822b485465bb431b73dec4f7e724dbe382375db435608f4033ab

d91b80430038c8f338d63c0fdb59ffe1bf16f35b1885fcf8c197b70078f980bb

85fdb7ce03c933604e80eada1e61943e56365a074288d2e925929649dcab4348

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 j5gnpfweguiwerbngpiutbgn0iutb0pfwbdfsfef (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 j5gnpfweguiwerbngpiutbgn0iutb0pfwbdfsfef across your stack and pipelines.
If you installed it — respond
Remove j5gnpfweguiwerbngpiutbgn0iutb0pfwbdfsfef 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 j5gnpfweguiwerbngpiutbgn0iutb0pfwbdfsfef 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 j5gnpfweguiwerbngpiutbgn0iutb0pfwbdfsfef 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. j5gnpfweguiwerbngpiutbgn0iutb0pfwbdfsfef 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

2024-10-lokopoil23

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

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