Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Red Canary, a Zscaler company » HUNREDEXP1768977371

Incident Score: Analysis & Impact (HUNREDEXP1768977371)

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

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-21
Company Score Before Incident678 / 1000
Company Score After Incident657 / 1000
INCIDENT NUMBERHUNREDEXP1768977371
Type of Cyber IncidentCyber Attack
ATTACK VECTORWeaponized ZIP files with malicious JScript payloads
DATA EXPOSEDNA
INCIDENT DATE31/10/2025
STATUSOngoing

Key Highlights From The Incident Analysis

  • Timeline of Red Canary, a Zscaler company'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 Red Canary, a Zscaler company 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 Red Canary, a Zscaler company breach identified under incident ID HUNREDEXP1768977371.

The analysis begins with a detailed overview of Red Canary, a Zscaler company's information like the linkedin page: https://www.linkedin.com/company/redcanary, the number of followers: 77986, the industry type: Computer and Network Security and the number of employees: 404 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 678 and after the incident was 657 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 Red Canary, a Zscaler company and their customers.

On 01 November 2025, a cybersecurity incident called "Gootloader’s Sophisticated Anti-Detection Tactics Exposed in Latest Campaign" came to light.

A recent analysis by Huntress and Expel reveals how the Gootloader malware leverages deliberately malformed ZIP archives to evade security tools while maintaining functionality for targeted victims.

Impact assessments are still underway, so the full scope is not yet clear.

Formal response steps have not been shared publicly yet.

The case underscores how Ongoing, teams are taking away lessons such as Gootloader's use of malformed ZIP archives highlights the need for improved detection of non-standard archive structures and monitoring of script-based execution chains, and recommending next steps like Monitor for wscript.exe executing JScript from temp directories, Detect ZIP archives with >100 PK headers or truncated EOCD records and Inspect LNK files in Startup folders for persistence.

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 Phishing: Spearphishing Attachment (T1566.001) with high confidence (90%), with evidence including weaponized ZIP files containing malicious JScript payloads, and indiana_Animal_Protection_Laws_Guide.js and User Execution: Malicious File (T1204.002) with high confidence (90%), with evidence including victims extract and run the JScript file, and windows Script Host (WScript) processes it. Under the Execution tactic, the analysis identified Command and Scripting Interpreter: JavaScript (T1059.007) with high confidence (95%), with evidence including malicious JScript payloads (e.g., .js files), and wScript processes JScript from AppData\Local\Temp and Command and Scripting Interpreter: PowerShell (T1059.001) with high confidence (90%), with evidence including obfuscated PowerShell commands to establish C2, and cScript launches script spawning PowerShell. Under the Persistence tactic, the analysis identified Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder (T1547.001) with high confidence (90%), with evidence including lNK shortcuts in Startup folder, and nTFS short filenames (e.g., FILENA~1.js). Under the Defense Evasion tactic, the analysis identified Obfuscated Files or Information (T1027) with high confidence (95%), with evidence including malformed ZIP archives with nested structures, and xOR-encoded data blobs decoded by browsers, Obfuscated Files or Information: Software Packing (T1027.002) with moderate to high confidence (80%), with evidence including 500–1,000 nested ZIP files, and truncated EOCD records violating ZIP standards, Masquerading: Match Legitimate Name or Location (T1036.005) with moderate to high confidence (80%), with evidence including indiana_Animal_Protection_Laws_Guide.js, and legitimate-sounding filenames, Deobfuscate/Decode Files or Information (T1140) with moderate to high confidence (80%), with evidence including xOR-encoded data blobs decoded by browsers, and obfuscated PowerShell commands, and Signed Binary Proxy Execution: Rundll32 (T1218.011) with lower confidence (30%), supported by evidence indicating potential use of native Windows utilities for execution (implied). Under the Command and Control tactic, the analysis identified Application Layer Protocol: Web Protocols (T1071.001) with moderate to high confidence (80%), with evidence including establish command-and-control (C2) communications, and powerShell processes with obfuscated C2 commands. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (70%), with evidence including initial access broker facilitating Rhysida ransomware, and c2 communications established via PowerShell. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Phishing: Spearphishing Attachment (90%)
User Execution: Malicious File (90%)
Execution
Command and Scripting Interpreter: JavaScript (95%)
Command and Scripting Interpreter: PowerShell (90%)
Persistence
Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder (90%)
Defense Evasion
Obfuscated Files or Information (95%)
Obfuscated Files or Information: Software Packing (80%)
Masquerading: Match Legitimate Name or Location (80%)
Deobfuscate/Decode Files or Information (80%)
Signed Binary Proxy Execution: Rundll32 (30%)
Command and Control
Application Layer Protocol: Web Protocols (80%)
Exfiltration
Exfiltration Over C2 Channel (70%)

Sources & References