Instagram Data Leak Update

-

 


Instagram Data Leak

What Happened?

  • Cybersecurity firm Malwarebytes discovered a dataset containing personal information from approximately 17.5 million Instagram accounts circulating on dark web forums.
  • The leaked data reportedly includes:
    • Usernames
    • Email addresses
    • Phone numbers
    • Partial physical addresses
    • In some cases, location details. 

How Did It Occur?

  • The data appears to have been scraped via Instagram’s API, likely exploiting weaknesses in rate-limiting or privacy safeguards.
  • A threat actor using the alias “Solonik” posted the dataset on BreachForums, claiming it originated from a 2024 API leak.
  • Meta (Instagram’s parent company) denies any breach of internal systems, stating that the surge in password reset emails was due to a bug that allowed external parties to trigger reset requests, not unauthorized access.

Risks to Users

  • Phishing & Social Engineering: Attackers can craft convincing messages using real account details.
  • SIM-Swapping & Account Takeover: Exposed phone numbers and emails make these attacks easier.
  • Credential Stuffing: If passwords are reused across platforms, attackers may exploit other accounts.
  • Identity Theft: Combining leaked data points enables detailed profiling for fraud. 

What Meta Says

  • Meta insists no passwords were leaked and accounts remain secure.
  • The company fixed the bug causing mass password reset emails and advises users to ignore unsolicited reset requests.

What Should You Do?

  1. Enable Two-Factor Authentication (2FA) via an authenticator app (not SMS).
  2. Change your password if you suspect unusual activity.
  3. Ignore suspicious password reset emails—navigate directly to Instagram settings if concerned.
  4. Review login activity in Instagram’s security settings.
  5. Stay alert for phishing attempts via email, SMS, or DMs.



Popular posts from this blog

WSUS CVE-2025-59287 Mitigation

-
Image
CVE-2025-59287 is a critical Remote Code Execution (RCE) vulnerability affecting Windows Server Update Services (WSUS) . Here's a detailed breakdown of what it is, how it works, and what you should do about it: Overview Disclosed: October 2025 Patch Tuesday CVSS Score: 9.8 (Critical) Affected Systems: Windows Server 2012 through 2025 (including Server Core installations) Exploitability: Microsoft rates it as “Exploitation More Likely” Technical Details The vulnerability arises from unsafe deserialization of untrusted data in WSUS. Specifically, the GetCookie() endpoint in WSUS processes encrypted AuthorizationCookie objects without proper type validation. The deserialization occurs via .NET BinaryFormatter , which is known to be insecure when handling untrusted input. Attackers can send a crafted SOAP request to WSUS over port 8530 , containing a malicious AuthorizationCookie . The cookie is decrypted using a hardcoded AES key and then deserialized, allow...
Read more

CVE-2025-58034 Fortinet Warnings and Mitigation

-
Image
Type: OS Command Injection vulnerability (CWE-78) Affected Product: Fortinet FortiWeb (Web Application Firewall) Affected Versions: 8.0.0 – 8.0.1 7.6.0 – 7.6.5 7.4.0 – 7.4.10 7.2.0 – 7.2.11 7.0.0 – 7.0.11 [nvd.nist.gov] , [cvedetails.com] Description The vulnerability is caused by improper neutralization of special elements used in OS commands . An authenticated attacker can exploit this flaw by sending crafted HTTP requests or CLI commands , allowing them to execute arbitrary code on the underlying system. This can compromise the integrity, confidentiality, and availability of the device. [nvd.nist.gov] , [cvedetails.com] Severity CVSS v3.1 Base Score: 7.2 (High) Vector: AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Attack Vector: Network Attack Complexity: Low Privileges Required: High User Interaction: None Impact: High on Confidentiality, Integrity, and Availability [cvedetails.com] Exploitation Status Actively Exploited: Yes. Fortinet confirmed expl...
Read more

Cloud Infrastructures are Having a Bad Week

-
Image
  Today’s disruptions across Microsoft Azure and Amazon Web Services (AWS) were significant, but they’re not signs of cloud computing’s demise. Instead, they underscore the risks of centralization and the importance of designing systems that can withstand provider-level failures. What happened today? • Microsoft Azure outage: Azure’s Front Door service suffered a major disruption due to a misconfiguration, impacting services like Outlook, Xbox, Microsoft 365, and even third-party platforms like Starbucks and Alaska Airlines. The Azure website states a little more than disruption. "Azure Front Door - Connectivity issues - Observing recovery Starting at approximately 16:00 UTC on 29 October 2025, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue. Affected Azure services may have included, but were not limited to: App S...
Read more