ADT Data Breach

-


ADT suffered a confirmed data breach on April 20, 2026, linked to the ShinyHunters extortion group, exposing customer names, phone numbers, and addresses — with some cases including dates of birth and the last four digits of SSNs or Tax IDs. No financial data or home security systems were compromised.

ADT detected unauthorized access to customer and prospective customer data on April 20, 2026. The intrusion was quickly terminated, and ADT launched a forensic investigation with third‑party cybersecurity experts while notifying law enforcement.

The threat actor ShinyHunters claimed responsibility, stating they stole over 10 million records and threatened to leak the data unless ADT paid a ransom. ADT has not confirmed the 10M figure but acknowledges a breach occurred.

What Data Was Exposed

ADT states the compromised data includes:

  • Names

  • Phone numbers

  • Addresses

  • In a small percentage of cases:

    • Dates of birth

    • Last four digits of SSNs or Tax IDs

Critically:

  • No payment information (bank accounts, credit cards) was accessed.

  • No ADT home security systems or monitoring services were affected.


How the Attack Happened

ShinyHunters told investigators they gained access through a voice‑phishing (vishing) attack that compromised an employee’s Okta SSO account. From there, they accessed ADT’s Salesforce environment and exfiltrated data.

This aligns with ShinyHunters’ broader campaign targeting Microsoft Entra, Okta, and Google SSO accounts across multiple industries.

Risks to Customers

Even though financial data wasn’t exposed, the stolen PII can still enable:

  • Phishing and social‑engineering attacks

  • Identity theft attempts

  • Account takeover attempts using personal details

ADT has notified affected individuals and is offering identity protection services.

Recommended Actions

If you or your organization uses ADT services, consider:

  • Monitoring for phishing attempts using your ADT‑related info

  • Enabling fraud alerts with credit bureaus

  • Reviewing account activity for unusual behavior

  • Using strong MFA on all accounts, especially those tied to home or business security


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

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

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