Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

jupiter-sdkPyPI

Advisory published Updated

jupiter-sdk is a confirmed malicious PyPI package (MAL-2026-10196) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jupiter-sdk (PyPI)

MAL-2026-10196
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall jupiter-sdk

What this malware does

On import jupiter_sdk, the package's top-level init.py fetches a payload over HTTPS from a public IPFS gateway (https://gateway.pinata.cloud/ipfs/QmP2RrfNCNabLzPYncMGgFwAmttDafczpJLS8oxvQRBVqg), passes the response body directly to exec(), and invokes a main() function from the executed namespace, with errors silently swallowed. The URL is content-addressed to an IPFS CID with no signature or hash verification of the executed content beyond the CID, and the fetched code is not shipped with the package. The package presents itself as a 'Jupiter DEX Aggregator SDK' but its exported API (get_quote, get_token_list, get_routes) returns hardcoded dummy values and performs no real Jupiter calls, so the only functional behavior on install/import is the remote code loader. The name resembles the widely used Jupiter aggregator ecosystem while performing arbitrary remote code execution against any environment that imports it.

During import, the code downloads and executes a remote script. The script collects sensitive files, including cryptocurrency wallet private keys and seeds, SSH keys, dotenv files and uploads them to IPFS. After that, it communicates with C2 and awaits further commands to execute.

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

Campaign: 2026-07-metemask-sdk

Reasons (based on the campaign):

  • files-exfiltration

  • typosquatting

  • exfiltration-ssh-keys

  • crypto-related

  • Downloads and executes a remote malicious script.

  • exfiltration-crypto

  • The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.

  • uses:ipfs

Malicious versions

2 flagged
0.1.00.1.1

Indicators of compromise (SHA-256)

4fe90c74194fd64c35606cd24835a77493495efe29bf6ad593cc4fa5a20f58be
669a4db1a6e8dcc53ea15154554c964585c7d06e97db5a5db522700e174ef721
f8e0901ca45da110106c60f288b0166fc51c348a44569d7e7ff22af3d19deafe

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for jupiter-sdk (2 malicious versions).

  2. If you installed it — respond

    jupiter-sdk 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.

  3. Did it already run?

    If jupiter-sdk 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. jupiter-sdk on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-07-metemask-sdkIN-MAL-2026-009776IN-MAL-2026-009777

References

Credits

  • Amazon Inspector · finder
  • Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

jupiter-sdk (PyPI) malicious package — MAL-2026-10196 | O3 Security