Incident Score: Analysis & Impact (SUPPRO1770195532)
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 Supabase's Vulnerability 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 Supabase 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 Supabase breach identified under incident ID SUPPRO1770195532.
The analysis begins with a detailed overview of Supabase's information like the linkedin page: https://www.linkedin.com/company/supabase, the number of followers: 81528, the industry type: IT Services and IT Consulting and the number of employees: 270 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 754 and after the incident was 751 with a difference of -3 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 Supabase and their customers.
Moltbook recently reported "Moltbook: AI Social Network Exposed 1.5M API Tokens in Major Security Flaw", a noteworthy cybersecurity incident.
Moltbook, a viral social platform designed exclusively for AI agents, suffered a critical security breach after researchers discovered a misconfigured Supabase database exposing sensitive user data.
The disruption is felt across the environment, affecting Moltbook production database, client-side JavaScript, and exposing 1.5M API tokens, 35,000 email addresses, 4,060 private messages (including plaintext OpenAI API keys), with nearly 1.5M API tokens, 35,000 email addresses, 4,060 private messages records at risk.
In response, moved swiftly to contain the threat with measures like Enabled Supabase Row Level Security (RLS) policies, and began remediation that includes Secured database, deleted accessed data post-remediation.
The case underscores how Resolved, teams are taking away lessons such as Risks in AI-driven development where speed outpaces security; need for secure defaults in AI-built applications, and recommending next steps like Implement proper security safeguards, avoid hardcoded credentials, enable Row Level Security (RLS) by default, and verify AI agent autonomy.
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 Exploit Public-Facing Application (T1190) with high confidence (90%), supported by evidence indicating misconfigured Supabase database exposing sensitive user data and External Remote Services (T1133) with moderate to high confidence (80%), supported by evidence indicating hardcoded Supabase API key in client-side JavaScript granting unauthenticated access. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Credentials In Files (T1552.001) with high confidence (95%), supported by evidence indicating hardcoded Supabase API key in the platform’s client-side JavaScript and Steal Application Access Token (T1528) with high confidence (90%), supported by evidence indicating 1.5M API tokens exposed, allowing full account takeovers. Under the Collection tactic, the analysis identified Data from Information Repositories (T1213) with high confidence (90%), supported by evidence indicating full read-and-write access to the platform’s production database and Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating 35,000 email addresses, 4,060 private messages exposed. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (70%), supported by evidence indicating researchers discovered misconfigured database exposing sensitive data and Transfer Data to Cloud Account (T1537) with moderate confidence (60%), supported by evidence indicating database accessible via hardcoded API key in client-side code. Under the Impact tactic, the analysis identified Network Denial of Service (T1498) with moderate confidence (50%), supported by evidence indicating potential unauthorized data modification or malicious content injection and Data Manipulation: Stored Data Manipulation (T1565.001) with moderate to high confidence (80%), supported by evidence indicating write access enabled attackers to modify posts or inject malicious content. Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1562.001) with moderate to high confidence (70%), supported by evidence indicating lack of Row Level Security (RLS) policies in Supabase database. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Supabase Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/supabase/incident/SUPPRO1770195532
- Supabase CyberSecurity Rating page: https://www.rankiteo.com/company/supabase
- Supabase Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/suppro1770195532-supabase-moltbook-vulnerability-february-2026/
- Supabase CyberSecurity Score History: https://www.rankiteo.com/company/supabase/history
- Supabase CyberSecurity Incident Source: https://www.wiz.io/blog/exposed-moltbook-database-reveals-millions-of-api-keys
- 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