Which versions of juphelp are malicious?

The following PyPI versions of juphelp are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate juphelp if I installed it?

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

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

Yes — juphelp 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 juphelp 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 juphelp (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging juphelp across your stack and pipelines.

Malicious package

juphelpPyPI

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

MAL-2024-12293

Immediate action

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

pip uninstall juphelp

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.0

Indicators of compromise (SHA-256)

08e4d91a0927681aeb85d052531c0e1943924f1cdc0d5dc72988a4a57a811267

11cd911a4d43440f44f1eadb92d5d8deda2dc85af9e4a5cf9b99e90918ffad07

7c1c7412f1dad777d6f003f5560ac9fd09aa0cc3cb4e6987cbbbe395a6586b37

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 juphelp (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging juphelp across your stack and pipelines.
If you installed it — respond
juphelp 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 juphelp 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 juphelp 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. juphelp on PyPI has been identified as a malicious package (version 0.1.0 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 juphelp-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