Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Amazon Web Services (AWS) » LIMAMA1777312775

Incident Score: Analysis & Impact (LIMAMA1777312775)

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

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-8
Company Score Before Incident613 / 1000
Company Score After Incident605 / 1000
INCIDENT NUMBERLIMAMA1777312775
Type of Cyber IncidentCyber Attack
ATTACK VECTORMicrosoft Teams (Social Engineering), Email Bombing, Fake Software Installation (AWS S3)
DATA EXPOSEDCredentials, Active Directory Databases (NTDS.dit),...
INCIDENT DATE23/04/2026
STATUSOngoing

Key Highlights From The Incident Analysis

  • Timeline of Amazon Web Services (AWS)'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 Amazon Web Services (AWS) 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 Amazon Web Services (AWS) breach identified under incident ID LIMAMA1777312775.

The analysis begins with a detailed overview of Amazon Web Services (AWS)'s information like the linkedin page: https://www.linkedin.com/company/amazon-web-services, the number of followers: 10600547, the industry type: IT Services and IT Consulting and the number of employees: 153837 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 613 and after the incident was 605 with a difference of -8 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 Amazon Web Services (AWS) and their customers.

On 24 April 2026, a cybersecurity incident called "New Threat Cluster UNC6692 Exploits Microsoft Teams to Breach Corporate Networks" came to light.

Mandiant and Google Threat Intelligence Group uncovered a previously unknown threat cluster, UNC6692, which has been active since late December 2025, impersonating IT help desk workers via Microsoft Teams to infiltrate corporate networks.

The disruption is felt across the environment, affecting Corporate Networks, Domain Controllers and User Workstations, and exposing Credentials, Active Directory Databases (NTDS.dit) and Registry Hives.

In response, and began remediation that includes Audit Microsoft Teams external access policies and Implement secondary verification for help desk requests.

The case underscores how Ongoing, teams are taking away lessons such as The incident highlights the risks of default Microsoft Teams settings allowing external messaging, the targeting of senior employees with elevated privileges, and the use of legitimate cloud services (AWS S3, Heroku) for malicious activities, and recommending next steps like Restrict Microsoft Teams external access via admin policies or PowerShell, Implement secondary verification for IT help desk requests and Deploy YARA rules for SNOW malware detection, with advisories going out to stakeholders covering Security teams advised to audit Teams policies and implement secondary verification for help desk requests.

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 Link (T1566.002) with high confidence (90%), supported by evidence indicating microsoft Teams messages from external accounts posing as IT support, Phishing: Spearphishing Attachment (T1566.001) with moderate to high confidence (70%), supported by evidence indicating fake Mailbox Repair and Sync Utility hosted on AWS S3, and Supply Chain Compromise: Compromise Software Supply Chain (T1195.002) with moderate confidence (60%), supported by evidence indicating supply chain such as true, use of AWS S3 for malware hosting. Under the Execution tactic, the analysis identified User Execution: Malicious File (T1204.002) with high confidence (90%), supported by evidence indicating victims tricked into installing fake Mailbox Repair and Sync Utility, Command and Scripting Interpreter: JavaScript (T1059.007) with moderate to high confidence (80%), supported by evidence indicating sNOWBELT such as JavaScript-based Chromium extension, and Command and Scripting Interpreter: Python (T1059.006) with moderate to high confidence (80%), supported by evidence indicating sNOWGLAZE such as Python-based WebSocket tunneler. Under the Persistence tactic, the analysis identified Browser Extensions (T1176) with moderate to high confidence (80%), supported by evidence indicating sNOWBELT such as JavaScript-based Chromium extension (MS Heartbeat) and Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder (T1547.001) with moderate to high confidence (70%), supported by evidence indicating sNOWBASIN such as Persistent backdoor enabling remote command execution. Under the Privilege Escalation tactic, the analysis identified Valid Accounts: Domain Accounts (T1078.002) with high confidence (90%), supported by evidence indicating stolen credentials used for pass-the-hash to compromise domain controllers and OS Credential Dumping: LSASS Memory (T1003.001) with high confidence (90%), supported by evidence indicating extracts LSASS memory via Windows Task Manager. Under the Defense Evasion tactic, the analysis identified Masquerading: Match Legitimate Name or Location (T1036.005) with high confidence (90%), supported by evidence indicating sNOWGLAZE masquerades as Microsoft Edge traffic, Application Layer Protocol: Web Protocols (T1071.001) with moderate to high confidence (80%), supported by evidence indicating c2 communication via AES-GCM-encrypted AWS S3 traffic, Hide Artifacts: Email Hiding Rules (T1564.008) with moderate to high confidence (70%), supported by evidence indicating email bombing to overwhelm targets, and Ingress Tool Transfer (T1105) with moderate to high confidence (80%), supported by evidence indicating fake utility hosted on AWS S3 for credential harvesting. Under the Credential Access tactic, the analysis identified Input Capture: GUI Input Capture (T1056.002) with high confidence (90%), supported by evidence indicating deceptive double-entry password prompt for credential harvesting, OS Credential Dumping: NTDS (T1003.003) with high confidence (90%), supported by evidence indicating fTK Imager used to extract Active Directory databases (NTDS.dit), and Credentials from Password Stores: Credentials from Web Browsers (T1555.003) with moderate to high confidence (70%), supported by evidence indicating sNOWBELT such as Chromium extension for credential access. Under the Discovery tactic, the analysis identified Account Discovery: Domain Account (T1087.002) with moderate to high confidence (80%), supported by evidence indicating internal reconnaissance post-compromise and Remote System Discovery (T1018) with moderate to high confidence (80%), supported by evidence indicating lateral movement to domain controllers. Under the Lateral Movement tactic, the analysis identified Use Alternate Authentication Material: Pass the Hash (T1550.002) with high confidence (90%), supported by evidence indicating pass-the-hash techniques to compromise domain controllers and Remote Services: Remote Desktop Protocol (T1021.001) with moderate to high confidence (70%), supported by evidence indicating lateral movement within corporate networks. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating extracts NTDS.dit, registry hives, and LSASS memory and Screen Capture (T1113) with moderate to high confidence (80%), supported by evidence indicating sNOWBASIN enables screenshot capture. Under the Command and Control tactic, the analysis identified Application Layer Protocol: Web Protocols (T1071.001) with high confidence (90%), supported by evidence indicating c2 via AES-GCM-encrypted AWS S3 traffic in 30-minute intervals, Web Service: Bidirectional Communication (T1102.002) with moderate to high confidence (80%), supported by evidence indicating sNOWGLAZE such as WebSocket tunneler for secure proxy, and Dynamic Resolution: Domain Generation Algorithms (T1568.002) with moderate confidence (60%), supported by evidence indicating use of legitimate cloud services (AWS S3, Heroku) for C2. Under the Exfiltration tactic, the analysis identified Exfiltration Over Web Service: Exfiltration to Cloud Storage (T1567.002) with high confidence (90%), supported by evidence indicating data exfiltrated via asynchronous PUT requests to attacker-controlled S3 buckets and Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), supported by evidence indicating exfiltration via LimeWire and AWS S3. Under the Impact tactic, the analysis identified Defacement: Internal Defacement (T1491.001) with moderate confidence (50%), supported by evidence indicating internal reconnaissance and lateral movement and Data Destruction (T1485) with lower confidence (40%), supported by evidence indicating potential data destruction during lateral movement. 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 Link (90%)
Phishing: Spearphishing Attachment (70%)
Supply Chain Compromise: Compromise Software Supply Chain (60%)
Execution
User Execution: Malicious File (90%)
Command and Scripting Interpreter: JavaScript (80%)
Command and Scripting Interpreter: Python (80%)
Persistence
Browser Extensions (80%)
Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder (70%)
Privilege Escalation
Valid Accounts: Domain Accounts (90%)
OS Credential Dumping: LSASS Memory (90%)
Defense Evasion
Masquerading: Match Legitimate Name or Location (90%)
Application Layer Protocol: Web Protocols (80%)
Hide Artifacts: Email Hiding Rules (70%)
Ingress Tool Transfer (80%)
Credential Access
Input Capture: GUI Input Capture (90%)
OS Credential Dumping: NTDS (90%)
Credentials from Password Stores: Credentials from Web Browsers (70%)
Discovery
Account Discovery: Domain Account (80%)
Remote System Discovery (80%)
Lateral Movement
Use Alternate Authentication Material: Pass the Hash (90%)
Remote Services: Remote Desktop Protocol (70%)
Collection
Data from Local System (90%)
Screen Capture (80%)
Command and Control
Application Layer Protocol: Web Protocols (90%)
Web Service: Bidirectional Communication (80%)
Dynamic Resolution: Domain Generation Algorithms (60%)
Exfiltration
Exfiltration Over Web Service: Exfiltration to Cloud Storage (90%)
Exfiltration Over C2 Channel (80%)
Impact
Defacement: Internal Defacement (50%)
Data Destruction (40%)

Sources & References