Which versions of juphelper are malicious?

The following PyPI versions of juphelper are flagged malicious: 0.1.6. Treat any of these as compromised.

How do I remediate juphelper if I installed it?

juphelper is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

Yes — juphelper is associated with the 2024-08-sleipnirbrowser-web3 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 juphelper 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 juphelper (version 0.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging juphelper across your stack and pipelines.

Malicious package

juphelperPyPI

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

MAL-2024-12294

Immediate action

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

pip uninstall juphelper

What this malware does

Once run, downloads and install from sleipnirbrowser[.]org a suspicious executable pretending to be a webbrowser. This website appears to be a scam using some kind of crypto tokens, and trying to impersonate a legitimate Slepnir web browser (https://en.wikipedia.org/wiki/Sleipnir_(web_browser)).

Later versions switched to install a software identified as LUMMA infostealer (e.g. https://tria.ge/240817-whze2aydkc), hidden in different executables

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2024-08-sleipnirbrowser-web3

Reasons (based on the campaign):

Downloads and executes a remote executable.
dependency-confusion
crypto-related
modify-system-without-consent
impersonation

Malicious versions

1 flagged

0.1.6

Indicators of compromise (SHA-256)

0a418871b642b1754cf5d24beb0b7fd551d8c6b8412fa934994915196de64fda

9bc13ee7427735e24063e780c1b868c131887f9f77c858325e1c81353ee4cd3a

4e7ec61f824bc53ef5fff80f746f1fe0c362d98fe24c3d5fabdf71c51592fec6

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for juphelper (version 0.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging juphelper across your stack and pipelines.
If you installed it — respond
juphelper is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If juphelper 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 juphelper 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. juphelper on PyPI has been identified as a malicious package (version 0.1.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-08-sleipnirbrowser-web3

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks juphelper-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring