Incident Score: Analysis & Impact (NPMSOLETH1774427254)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of npm, Inc.'s Cyber Attack and lateral movement inside company's environment.
- Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
- How Rankiteo’s incident engine converts technical details into a normalized incident score.
- How this cyber incident impacts npm, Inc. Rankiteo cyber scoring and cyber rating.
- Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.
Full Incident Analysis Transcript
In this Rankiteo incident briefing, we review the npm, Inc. breach identified under incident ID NPMSOLETH1774427254.
The analysis begins with a detailed overview of npm, Inc.'s information like the linkedin page: https://www.linkedin.com/company/npm-inc-, the number of followers: 11914, the industry type: Software Development and the number of employees: 18 employees
After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 512 and after the incident was 491 with a difference of -21 which is could be a good indicator of the severity and impact of the incident.
In the next step of the video, we will analyze in more details the incident and the impact it had on npm, Inc. and their customers.
On 23 March 2026, Solana and Ethereum developers disclosed Supply Chain Attack issues under the banner "Malicious npm Packages Target Solana and Ethereum Developers in Supply Chain Attack".
A recent supply chain attack has compromised cryptocurrency developers by distributing five malicious npm packages that steal wallet private keys and exfiltrate them to a Telegram-based command-and-control (C2) server.
The disruption is felt across the environment, affecting Node.js 18+ environments, and exposing Wallet private keys.
In response, moved swiftly to contain the threat with measures like Takedown requests for malicious npm packages, and began remediation that includes Remove affected packages and treat exposed keys as compromised, and stakeholders are being briefed through Developer advisories to remove packages.
The case underscores how Ongoing (malicious packages partially removed), and recommending next steps like Remove affected npm packages, treat exposed keys as compromised, and verify dependencies for typosquatting/dependency confusion risks, with advisories going out to stakeholders covering Developers advised to remove affected packages and rotate compromised keys.
Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.
The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.
MITRE ATT&CK® Correlation Analysis
Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Supply Chain Compromise: Compromise Software Dependencies and Development Tools (T1195.001) with high confidence (95%), with evidence including malicious npm packages impersonating legitimate libraries, and typosquatting and dependency confusion attack vectors. Under the Execution tactic, the analysis identified Command and Scripting Interpreter: JavaScript (T1059.007) with high confidence (90%), supported by evidence indicating malicious code in npm packages targeting Node.js 18+ environments. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Private Keys (T1552.004) with high confidence (95%), with evidence including packages designed to intercept private key operations, and wallet private keys stolen via hijacked Base58 decode() calls. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating private keys stolen from local systems via malicious npm packages. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (95%), with evidence including stolen keys sent to hardcoded Telegram bot (@Test20131_Bot), and data exfiltration to Telegram C2 server. Under the Command and Control tactic, the analysis identified Web Service: Bidirectional Communication (T1102.002) with high confidence (90%), with evidence including telegram-based command-and-control (C2) server, and attack infrastructure relies solely on Telegram bot. Under the Defense Evasion tactic, the analysis identified Obfuscated Files or Information (T1027) with moderate to high confidence (85%), with evidence including obfuscation techniques including array-rotation ciphers, and malicious code concealed in npm packages and Masquerading: Match Legitimate Name or Location (T1036.005) with high confidence (90%), supported by evidence indicating packages impersonate legitimate crypto libraries (e.g., raydium-bs58, ethersproject-wallet). Under the Impact tactic, the analysis identified Resource Hijacking (T1496) with moderate to high confidence (80%), supported by evidence indicating attackers drain compromised cryptocurrency wallets. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- npm, Inc. Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/npm-inc-/incident/NPMSOLETH1774427254
- npm, Inc. CyberSecurity Rating page: https://www.rankiteo.com/company/npm-inc-
- npm, Inc. Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/npmsoleth1774427254-npm-solana-ethereum-cyber-attack-march-2026/
- npm, Inc. CyberSecurity Score History: https://www.rankiteo.com/company/npm-inc-/history
- npm, Inc. CyberSecurity Incident Source: https://gbhackers.com/five-malicious-npm-packages/
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf