Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Zapier » NPM1764705355

Incident Score: Analysis & Impact (NPM1764705355)

The details regarding individual company incidents & reports gives you full view from every side.

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-26
Company Score Before Incident745 / 1000
Company Score After Incident719 / 1000
Company LinkView Zapier Profile
INCIDENT NUMBERNPM1764705355
Type of Cyber IncidentCyber Attack
ATTACK VECTORMalicious NPM packages
DATA EXPOSED400,000 raw secrets exposed
INCIDENT DATE30/11/2025
STATUSOngoing

Key Highlights From The Incident Analysis

  • Timeline of Zapier'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 Zapier 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 Zapier breach identified under incident ID NPM1764705355.

The analysis begins with a detailed overview of Zapier's information like the linkedin page: https://www.linkedin.com/company/zapier, the number of followers: 344475, the industry type: Software Development and the number of employees: 1409 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 745 and after the incident was 719 with a difference of -26 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 Zapier and their customers.

NPM (Node Package Manager) recently reported "Shai-Hulud 2.0 NPM and GitHub Secrets Exposure", a noteworthy cybersecurity incident.

The second Shai-Hulud attack exposed around 400,000 raw secrets after infecting hundreds of packages in the NPM (Node Package Manager) registry and publishing stolen data in 30,000 GitHub repositories.

The disruption is felt across the environment, affecting NPM registry, GitHub repositories, and exposing 400,000 raw secrets exposed, with nearly 400,000 raw secrets records at risk.

Formal response steps have not been shared publicly yet.

The case underscores how Ongoing.

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 infecting hundreds of packages in the NPM registry, and self-propagating payload in NPM packages. Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1528) with high confidence (90%), with evidence including exposed around 400,000 raw secrets including GitHub tokens, and 60% of leaked NPM tokens still valid and Unsecured Credentials: Credentials In Files (T1552.001) with moderate to high confidence (85%), with evidence including contents.json file with GitHub usernames and tokens, and truffleSecrets.json containing TruffleHog scan results. Under the Lateral Movement tactic, the analysis identified Account Discovery: Cloud Account (T1087.004) with moderate to high confidence (80%), with evidence including identified account tokens using TruffleHog, and gitHub usernames and tokens exposed. Under the Impact tactic, the analysis identified Data Destruction (T1485) with moderate to high confidence (85%), supported by evidence indicating destructive mechanism that wiped the victim’s home directory and Defacement: Internal Defacement (T1491.001) with moderate to high confidence (70%), supported by evidence indicating injected a malicious script into the packages. Under the Exfiltration tactic, the analysis identified Transfer Data to Cloud Account (T1537) with high confidence (90%), with evidence including publishing stolen data in 30,000 GitHub repositories, and data exfiltration such as Yes. Under the Defense Evasion tactic, the analysis identified Obfuscated Files or Information (T1027) with moderate to high confidence (75%), with evidence including malicious script injected into packages, and self-propagating payload. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Sources & References