Scraped Data of 17.5 Million Instagram Users, Including Emails and Phone Numbers, Leaked on BreachForums

Data of 17.5 Million Instagram Users Leaked on Hacker Forum After Scraping Attack

HIGH
January 10, 2026
6m read
Data BreachPhishing

Impact Scope

People Affected

17.5 million

Industries Affected

TechnologyMedia and Entertainment

Related Entities

Threat Actors

Solonik

Organizations

Products & Tech

Instagram

Other

BreachForums

Full Report

Executive Summary

A dataset containing the personally identifiable information (PII) of an estimated 17.5 million Instagram users has been leaked on the notorious hacker forum, BreachForums. The data, posted by a threat actor known as "Solonik," appears to have been collected through large-scale data scraping of Instagram's public-facing APIs rather than a direct breach of Meta's internal systems. The leaked information includes full names, email addresses, phone numbers, and user IDs. This exposure places millions of users at immediate risk of sophisticated phishing campaigns, SIM swapping, and identity theft. The incident is compounded by a reported spike in fraudulent password reset attempts against Instagram accounts, indicating that malicious actors are actively exploiting the leaked data.


Breach Overview

  • Source of Leak: A threat actor named "Solonik" on BreachForums.
  • Data Size: Approximately 17.5 million user records.
  • Data Contents: Full names, email addresses, phone numbers, Instagram user IDs, and partial addresses.
  • Method: The data was reportedly obtained via data scraping, an automated technique used to harvest large amounts of information from websites and APIs. This suggests a potential weakness in Instagram's rate-limiting or anti-bot protections that allowed the actor to query so many profiles.
  • Date of Leak: The data appeared on BreachForums on January 7, 2026.

Following the leak, there has been a noticeable increase in malicious activity targeting Instagram users, particularly a wave of unsolicited password reset notifications. This indicates that other threat actors are using the email addresses and phone numbers from the leak to try to hijack accounts.


Technical Analysis

Data scraping is the primary technique behind this incident. It is distinct from a "hack" in that it doesn't necessarily involve bypassing security controls to access non-public data. Instead, it automates the process of collecting data that is already publicly or semi-publicly available.

  • API Abuse: The scraper likely exploited a legitimate or poorly documented API endpoint that returns user profile information. By automating requests to this API with millions of different user IDs, the actor could compile the massive dataset.
  • Failure of Protective Measures: The scale of this scraping operation suggests a failure of Instagram's defensive measures. Effective anti-scraping technologies typically include:
    • Rate Limiting: Restricting the number of requests a single IP address or API key can make in a given time.
    • Bot Detection: Using behavioral analysis and fingerprinting to identify and block automated scripts.
    • Data Obfuscation: Limiting the amount of PII returned by public-facing APIs.

MITRE ATT&CK TTPs

Tactic
Collection
Technique ID
Name
Search Open Technical Databases
Description
The threat actor likely enumerated user IDs and scraped data via a public API.
Tactic
Credential Access
Technique ID
Name
Credentials from Password Stores
Description
Following the leak, other actors are using the data to attempt account takeovers.
Tactic
Initial Access
Technique ID
Name
Phishing
Description
The leaked PII is ideal for crafting highly targeted and convincing phishing emails.

Impact Assessment

  • Increased Phishing and Scams: With access to names, emails, and phone numbers, attackers can launch highly personalized phishing campaigns (spear-phishing) that are more likely to succeed.
  • SIM Swapping Attacks: The availability of phone numbers linked to specific individuals increases the risk of SIM swapping, where an attacker tricks a mobile carrier into transferring a victim's phone number to a new SIM card, allowing them to intercept MFA codes sent via SMS.
  • Identity Theft: The combination of PII can be used to impersonate victims, open fraudulent accounts, or as a starting point for more comprehensive identity theft.
  • Account Takeover: The surge in password reset attempts shows that the data is being actively used to try to gain control of Instagram accounts for spam, fraud, or to demand a ransom.
  • Reputational Damage to Meta: The incident raises questions about the effectiveness of Instagram's privacy safeguards and its responsibility to protect user data, even if it is publicly accessible.

IOCs

  • Threat Actor: Solonik
  • Forum: BreachForums

Cyber Observables for Detection

For platform providers like Meta:

Type
network_traffic_pattern
Value
High-volume API requests from a single source
Description
A single IP or a small pool of IPs making an abnormally high number of requests to user profile API endpoints.
Context
API gateway and WAF logs.
Confidence
high
Type
other
Value
Sequential user ID enumeration
Description
API requests that appear to be iterating through user IDs in a sequential or predictable pattern.
Context
Application-level logging.
Confidence
high

Detection & Response

Recommendations for Instagram Users

  1. Enable Strong MFA: The single most important action is to enable multi-factor authentication on your Instagram account. Crucially, use an authenticator app (like Google Authenticator or Authy) instead of SMS-based MFA, as this protects against SIM swapping attacks.
  2. Change Your Password: Create a new, unique, and strong password for your Instagram account.
  3. Be Vigilant: Treat all unsolicited emails or messages, especially those related to your Instagram account, with extreme suspicion. Never click on password reset links you did not request yourself. Manually navigate to instagram.com to reset your password if you are concerned.
  4. Review Account Security: Check your Instagram account's login activity (Settings > Security > Login Activity) for any unrecognized sessions and log them out.

Mitigation

For Platform Providers (like Meta)

  1. Strengthen Anti-Scraping Controls: Implement more sophisticated bot detection and stricter, adaptive rate limiting on all public-facing APIs that return user data. This is a form of D3FEND Application Configuration Hardening (D3-ACH).
  2. Data Minimization: Review all API endpoints to ensure they only return the minimum data necessary for their function. Do not expose sensitive data like full email addresses or phone numbers through public APIs if possible.
  3. Proactive Monitoring: Actively monitor for and disrupt large-scale scraping operations, rather than waiting for the data to appear on hacker forums.
  4. Transparent Communication: Promptly and clearly communicate with users when a large-scale scraping incident is confirmed to have exposed their data, and provide clear guidance on protective measures.

Timeline of Events

1
January 7, 2026
A dataset of 17.5 million Instagram users is posted on BreachForums by the threat actor 'Solonik'.
2
January 10, 2026
Users report a surge in fraudulent password reset attempts, and news outlets begin covering the leak.
3
January 10, 2026
This article was published

MITRE ATT&CK Mitigations

Users should enable MFA, preferably using an authenticator app, to protect their accounts even if their password is stolen or reset.

Mapped D3FEND Techniques:

Educate users to be vigilant against phishing attempts that will leverage the leaked data and to never click on unsolicited password reset links.

D3FEND Defensive Countermeasures

For Instagram users affected by this leak, the most critical defensive action is to enable Multi-Factor Authentication immediately. Given that the leak includes phone numbers, which makes users vulnerable to SIM swapping, it is imperative to use an authenticator app (such as Google Authenticator, Microsoft Authenticator, or Authy) for MFA instead of SMS. An app-based code is generated on the device itself and is not susceptible to interception via SIM swapping. This single step provides a powerful layer of security that protects the account even if an attacker has the user's password, directly mitigating the primary risk from this data leak.

For platform providers like Meta, preventing future large-scale scraping requires robust Application Configuration Hardening on public-facing APIs. This involves implementing adaptive rate limiting that goes beyond simple per-IP thresholds. The system should analyze behavior, detecting and throttling sources that are systematically enumerating user IDs or making an unusually high number of profile requests. Furthermore, APIs should be configured with data minimization in mind; endpoints available to unauthenticated or low-trust clients should not return sensitive PII like email addresses or phone numbers. This combination of stricter access control and reduced data exposure on public APIs is the key technical countermeasure to prevent scraping at this scale.

Timeline of Events

1
January 7, 2026

A dataset of 17.5 million Instagram users is posted on BreachForums by the threat actor 'Solonik'.

2
January 10, 2026

Users report a surge in fraudulent password reset attempts, and news outlets begin covering the leak.

Sources & References

Instagram Data Breach Exposes Millions To Cyber Threats
Grand Pinnacle Tribune (grandpinnacletribune.com) January 10, 2026
17.5 Million Instagram Accounts Exposed in Major Data Leak
Cyberpress (cyberpress.com) January 10, 2026

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

Data LeakData ScrapingInstagramMetaBreachForumsPIIPhishingSIM Swapping

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.