Malicious code in @wagni_bot/jupiter-sdk (npm)
The @wagni_bot/jupiter-sdk npm package versions 1.0.0 and 1.2.0 is a malicious typosquatting package impersonating the legitimate Jupiter SDK for Solana. It contains no legitimate SDK functionality but instead executes a postinstall script that collects sensitive wallet files, seed phrases, mnemonics, and credentials from common user directories and browser profiles. The stolen data is exfiltrated to a hardcoded command-and-control server. This package targets developers working with Solana and Ethereum wallets by exploiting trust in the SDK namespace.
AI Analysis
Technical Summary
@wagni_bot/jupiter-sdk versions 1.0.0 and 1.2.0 is a malicious npm package that impersonates the Jupiter SDK namespace for Solana decentralized exchange development. Upon installation, its postinstall.js script automatically runs and searches the installer's home directory and common locations for wallet files related to Solana and Ethereum, browser extension states for MetaMask and Phantom, seed phrases and mnemonics identified by keyword and BIP39 wordlist matching, and various credential files including .env, .npmrc, .git-credentials, .netrc, AWS credentials, and SSH private keys. It collects up to 5000 bytes of each matched file and gathers host identity information such as hostname, user info, and home directory. All collected data is sent via HTTP POST to a hardcoded external server at 107.161.90.180 on port 7777. The package lacks any legitimate code or documentation and is purely designed as a credential stealer leveraging namespace impersonation to deceive developers.
Potential Impact
This malicious package compromises the confidentiality of sensitive cryptographic wallet materials and credentials by exfiltrating them to an attacker-controlled server. This can lead to theft of cryptocurrency assets, unauthorized access to cloud and development environments, and broader compromise of developer systems. The attack occurs silently during npm install, increasing the risk of unnoticed credential theft.
Mitigation Recommendations
No official patch or remediation is available for this malicious package. The best mitigation is to avoid installing @wagni_bot/jupiter-sdk versions 1.0.0 and 1.2.0. Developers should verify package authenticity before installation, prefer official SDK sources, and audit dependencies for typosquatting or suspicious packages. Remove any instances of these versions if found in projects and rotate any potentially compromised credentials or wallet keys. Monitor for suspicious network activity to the indicated C2 server IP and block it if possible.
Malicious code in @wagni_bot/jupiter-sdk (npm)
Description
The @wagni_bot/jupiter-sdk npm package versions 1.0.0 and 1.2.0 is a malicious typosquatting package impersonating the legitimate Jupiter SDK for Solana. It contains no legitimate SDK functionality but instead executes a postinstall script that collects sensitive wallet files, seed phrases, mnemonics, and credentials from common user directories and browser profiles. The stolen data is exfiltrated to a hardcoded command-and-control server. This package targets developers working with Solana and Ethereum wallets by exploiting trust in the SDK namespace.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
@wagni_bot/jupiter-sdk versions 1.0.0 and 1.2.0 is a malicious npm package that impersonates the Jupiter SDK namespace for Solana decentralized exchange development. Upon installation, its postinstall.js script automatically runs and searches the installer's home directory and common locations for wallet files related to Solana and Ethereum, browser extension states for MetaMask and Phantom, seed phrases and mnemonics identified by keyword and BIP39 wordlist matching, and various credential files including .env, .npmrc, .git-credentials, .netrc, AWS credentials, and SSH private keys. It collects up to 5000 bytes of each matched file and gathers host identity information such as hostname, user info, and home directory. All collected data is sent via HTTP POST to a hardcoded external server at 107.161.90.180 on port 7777. The package lacks any legitimate code or documentation and is purely designed as a credential stealer leveraging namespace impersonation to deceive developers.
Potential Impact
This malicious package compromises the confidentiality of sensitive cryptographic wallet materials and credentials by exfiltrating them to an attacker-controlled server. This can lead to theft of cryptocurrency assets, unauthorized access to cloud and development environments, and broader compromise of developer systems. The attack occurs silently during npm install, increasing the risk of unnoticed credential theft.
Mitigation Recommendations
No official patch or remediation is available for this malicious package. The best mitigation is to avoid installing @wagni_bot/jupiter-sdk versions 1.0.0 and 1.2.0. Developers should verify package authenticity before installation, prefer official SDK sources, and audit dependencies for typosquatting or suspicious packages. Remove any instances of these versions if found in projects and rotate any potentially compromised credentials or wallet keys. Monitor for suspicious network activity to the indicated C2 server IP and block it if possible.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10027
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50baa368715ace43584e6b
Added to database: 07/10/2026, 09:25:55 UTC
Last enriched: 07/10/2026, 10:13:32 UTC
Last updated: 07/30/2026, 18:24:53 UTC
Views: 28
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.