Incident Score: Analysis & Impact (TANNPM1777897814)
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 TANNPM1777897814.
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 354 and after the incident was 333 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 29 April 2026, Developers and organizations using the malicious 'tanstack' npm package disclosed Supply Chain Attack issues under the banner "Malicious 'tanstack' npm Package Exfiltrates Developer Credentials in Stealth Attack".
A malicious npm package named 'tanstack' was discovered executing a data exfiltration campaign, targeting developers by impersonating the legitimate TanStack ecosystem.
The disruption is felt across the environment, affecting Developer workstations with the malicious 'tanstack' npm package installed, and exposing Environment file contents (AWS keys, GitHub tokens, database credentials, API keys), system metadata, package version, and timestamp.
In response, moved swiftly to contain the threat with measures like Uninstallation of the malicious package and revocation of exposed credentials, and began remediation that includes Revocation of exposed credentials, rotation of API keys, and monitoring for unauthorized access.
The case underscores how Ongoing, teams are taking away lessons such as The incident underscores the risks of name-squatting attacks in open-source ecosystems and the importance of verifying package names and scopes before installation, and recommending next steps like Verify package names and scopes before installation to avoid name-squatting attacks, Monitor for suspicious postinstall scripts in npm packages and Rotate credentials immediately if the malicious package was installed, with advisories going out to stakeholders covering Developers who installed versions 2.0.4–2.0.7 of the 'tanstack' npm package should assume compromise and revoke exposed credentials.
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 Supply Chain (T1195.002) with high confidence (95%), supported by evidence indicating malicious npm package named tanstack...impersonating the legitimate TanStack ecosystem. Under the Execution tactic, the analysis identified Command and Scripting Interpreter: JavaScript (T1059.007) with high confidence (90%), supported by evidence indicating postinstall script that activated upon installation and User Execution: Malicious File (T1204.002) with moderate to high confidence (85%), supported by evidence indicating developers who installed versions 2.0.4–2.0.7 should assume compromise. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Credentials In Files (T1552.001) with high confidence (95%), supported by evidence indicating scanned for sensitive environment files including .env, .env.local, and .env.production and Steal Application Access Token (T1528) with moderate to high confidence (80%), supported by evidence indicating aWS keys, GitHub tokens, database credentials, API keys exfiltrated. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating exfiltrated their contents...including system metadata (Node.js version, OS, architecture). Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating exfiltrated their contents to an attacker-controlled Svix webhook endpoint and Exfiltration Over Web Service: Exfiltration to Cloud Storage (T1567.002) with moderate to high confidence (80%), supported by evidence indicating routing data through a legitimate webhooks-as-a-service platform (Svix). Under the Defense Evasion tactic, the analysis identified Masquerading: Match Legitimate Name or Location (T1036.005) with high confidence (95%), supported by evidence indicating impersonating the legitimate TanStack ecosystem...polished documentation and branding, Obfuscated Files or Information (T1027) with moderate to high confidence (85%), supported by evidence indicating disguised sensitive data under misleading field names like readme and agents, and Subvert Trust Controls: Code Signing (T1553.002) with moderate to high confidence (70%), supported by evidence indicating exploited confusion with the trusted @tanstack organization. Under the Reconnaissance tactic, the analysis identified Search Open Websites/Domains: Social Media (T1593.001) with moderate to high confidence (70%), supported by evidence indicating name-squatting attacks in open-source ecosystems...typo (e.g., tanstack vs. @tanstack/query). 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/TANNPM1777897814
- npm, Inc. CyberSecurity Rating page: https://www.rankiteo.com/company/npm-inc-
- npm, Inc. Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/tannpm1777897814-npm-tanstack-cyber-attack-april-2026/
- npm, Inc. CyberSecurity Score History: https://www.rankiteo.com/company/npm-inc-/history
- npm, Inc. CyberSecurity Incident Source: https://gbhackers.com/tanstack-package-abuses-postinstall/
- 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