Which versions of jupihelp are malicious?

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

How do I remediate jupihelp if I installed it?

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

If jupihelp was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is jupihelp part of a known attack campaign?

Yes — jupihelp 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 jupihelp across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jupihelp (version 0.1.0).

Malicious package

jupihelpPyPI

Advisory published Aug 10, 2024Updated Dec 12, 2025

jupihelp is a confirmed malicious PyPI package (MAL-2024-12295) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jupihelp (PyPI)

MAL-2024-12295

Immediate action

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

pip uninstall jupihelp

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)

240d54cfc52e68a10bad878dd6805ab7ac5a2e88e43189c76deec4c8914419f5

7bb124c218cd3a0340ff934eafc0d4c9cbf322b2428d8a868ed28703aeb38426

5d079153ce3953cf2b3c2d380503e1f6e3015d78265506817f729be119a179f0

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for jupihelp (version 0.1.0).
If you installed it — respond
jupihelp 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 jupihelp was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. jupihelp 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 jupihelp-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

Explore

All malware advisories How O3 detects malware Vulnerability database