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

Incident Score: Analysis & Impact (ONL1779863122)

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

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-121
Company Score Before Incident778 / 1000
Company Score After Incident657 / 1000
INCIDENT NUMBERONL1779863122
Type of Cyber IncidentBreach
ATTACK VECTORCompilation from prior leaks, public sources, and other security incidents
DATA EXPOSEDUsernames, email addresses, account activity...
INCIDENT DATE31/07/2025
STATUSUnverified

Key Highlights From The Incident Analysis

  • Timeline of OnlyFans's Breach 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 OnlyFans 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 OnlyFans breach identified under incident ID ONL1779863122.

The analysis begins with a detailed overview of OnlyFans's information like the linkedin page: https://www.linkedin.com/company/onlyfans, the number of followers: 81445, the industry type: Entertainment Providers and the number of employees: 5901 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 778 and after the incident was 657 with a difference of -121 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 OnlyFans and their customers.

OnlyFans recently reported "OnlyFans Data Leak Exposes 340 Million Records", a noteworthy cybersecurity incident.

Hackers claimed to possess 340 million records allegedly sourced from OnlyFans, including usernames, email addresses, account activity metrics, payment card details, and linked profiles.

The disruption is felt across the environment, and exposing Usernames, email addresses, account activity metrics, payment card details, linked profiles, with nearly 340 million (unverified) records at risk.

In response, and stakeholders are being briefed through Public denial of recent security compromise.

The case underscores how Unverified, and recommending next steps like Users should be cautious of phishing attacks and monitor for suspicious activity due to potential cross-referencing of exposed data with other breaches, with advisories going out to stakeholders covering Users should remain vigilant against phishing attempts and unauthorized account access.

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 Gather Victim Identity Information: Email Addresses (T1589.002) with moderate to high confidence (80%), supported by evidence indicating email addresses...allegedly sourced from OnlyFans and Gather Victim Identity Information: Credentials (T1589.001) with moderate to high confidence (70%), supported by evidence indicating payment card details, linked profiles exposed. Under the Credential Access tactic, the analysis identified Obtain Capabilities: Tool (T1588.002) with moderate confidence (60%), supported by evidence indicating database was compiled from prior leaks, public sources and Exploitation for Credential Access (T1212) with moderate confidence (50%), supported by evidence indicating cross-referencing emails with other breaches. Under the Collection tactic, the analysis identified Data from Information Repositories: Code Repositories (T1213.003) with moderate to high confidence (70%), supported by evidence indicating compiled from prior leaks, public sources, and other security incidents and Data from Local System (T1005) with moderate confidence (60%), supported by evidence indicating usernames, email addresses, account activity metrics exposed. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate confidence (50%), supported by evidence indicating 340 million records allegedly sourced from OnlyFans and Exfiltration Over Web Service: Exfiltration to Cloud Storage (T1567.002) with lower confidence (40%), supported by evidence indicating posted on a data leak forum. Under the Impact tactic, the analysis identified Gather Victim Network Information: Domain Properties (T1590.002) with moderate confidence (60%), supported by evidence indicating linked profiles, account activity metrics exposed and Defacement: Internal Defacement (T1491.001) with lower confidence (40%), supported by evidence indicating potential reputational damage due to unverified claims. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Gather Victim Identity Information: Email Addresses (80%)
Gather Victim Identity Information: Credentials (70%)
Credential Access
Obtain Capabilities: Tool (60%)
Exploitation for Credential Access (50%)
Collection
Data from Information Repositories: Code Repositories (70%)
Data from Local System (60%)
Exfiltration
Exfiltration Over C2 Channel (50%)
Exfiltration Over Web Service: Exfiltration to Cloud Storage (40%)
Impact
Gather Victim Network Information: Domain Properties (60%)
Defacement: Internal Defacement (40%)

Sources & References