Which versions of jupsolhelp are malicious?

The following PyPI versions of jupsolhelp are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3. Treat any of these as compromised.

How do I remediate jupsolhelp if I installed it?

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

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

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

Malicious package

jupsolhelpPyPI

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

MAL-2024-12297

Immediate action

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

pip uninstall jupsolhelp

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

4 flagged

0.1.00.1.10.1.20.1.3

Indicators of compromise (SHA-256)

df6fc89f19417b2f9b4012e3bbf2dec9dd2b07197b110d88cb781b7e78af6cbe

1bc1615518392665ccc36d8c24a0e8e57ffce1147dfc8604c723513c28061743

34f8998e5d39bd92bd5c97b2ed9d0074614ff0eae272117032b781f53885c6c2

68aa89d5dcbf47ece9a2cd4653811a12eaf3590c6268b096aeebb85b87266c98

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