data breaches
TPG Cybersecurity Under Fire After iiNet System Compromise
Contact data for ~280k email accounts and 1.7k modem passwords accessed; breach isolated to iiNet order system, company says
Australia’s TPG Telecom disclosed unauthorized access to an iiNet order management system, exposing around 280,000 active email addresses, ~20,000 landline numbers, ~10,000 names with street addresses and phone numbers, and ~1,700 modem setup passwords. The telco says no banking or ID documents were in the impacted system and the intrusion was contained after discovery.
SYDNEY — August 19, 2025. TPG Telecom, Australia’s No. 2 internet provider, is investigating a cyber incident that compromised an iiNet order management system (OMS) via stolen employee credentials, resulting in the extraction of customer contact data and a limited number of modem setup passwords. The company said sensitive identity and financial data were not held in the affected system, and it does not anticipate impact to broader TPG systems.
What was taken — and what wasn’t
Forensic work indicates historic service‐order records were accessed without authorization. Current findings point to the following extractions from iiNet systems: approximately 280,000 active iiNet email addresses, ~20,000 active landline phone numbers, ~10,000 user names with street addresses and phone numbers, and ~1,700 modem setup passwords. TPG emphasized that no credit card/banking data or customer ID documents (such as passports or driver’s licenses) were stored in the OMS.
How the intrusion happened
Early investigation suggests the attacker leveraged stolen credentials from one employee to access the OMS. After confirming the incident on Saturday, August 16, the company enacted its incident response plan and removed the access. TPG engaged external cybersecurity firms and notified Australian authorities, including the ACSC, NOCS, ASD, and OAIC.
“We unreservedly apologise to the iiNet customers impacted by this incident,” said TPG Telecom CEO Iñaki Berroeta, adding that outreach to affected and unaffected customers is underway with guidance and support. iinet.net.au
Technical analysis
Attack vector & foothold. Credential theft remains a top enterprise risk, often sourced from phishing, stealer malware, token theft, or password reuse. With valid credentials, adversaries can blend in with normal traffic, particularly against web apps or middleware that back office/field teams use to create and track orders. (TPG attributes the access to stolen employee credentials; the precise theft method has not been disclosed.)
System context. An Order Management System (OMS) in a telco typically sits between customer/CRM and network activation systems (OSS/BSS). It legitimately stores contact and service activation metadata (emails, phone numbers, service addresses, and sometimes device setup data) to authenticate and provision services. Because these data are operational—not financial—the impact skews toward targeted phishing and service manipulation rather than direct financial fraud.
Data sensitivity & exploitation risk.
- Email & phone lists can fuel high-credibility phishing/SMShing that references the victim’s ISP or service order history.
- Modem setup passwords (a small subset) could allow CPE reconfiguration if remote management is enabled or if the same password is reused on the device’s admin interface.
- Names + service addresses can support social engineering against help desks or delivery/installation workflows.
Containment posture. TPG states the breach appears isolated to the iiNet internal ordering system and does not impact broader TPG systems—suggesting either effective segmentation or early containment once the compromise was confirmed.
Guidance for customers
- Be extra vigilant for unsolicited contacts claiming to be from iiNet/TPG. Do not click links; navigate directly to official portals. (TPG is contacting both impacted and non-impacted customers.)
- Change your modem/admin passwords and ensure they’re unique. If your device supports it, disable remote administration or restrict it to your home network.
- Harden your email account(s): enable MFA, rotate passwords, and review mail-forwarding rules/filters that attackers often abuse post-phish.
- Watch for SIM-swap or voice-phishing attempts if your landline/phone number is on file.
- Refer to iiNet’s incident information page and support hotline for the latest instructions.
What telcos and large enterprises should do next (beyond the basics)
- Identity-first controls: Enforce FIDO2/WebAuthn for staff, conditional access with device posture checks, and block legacy auth.
- Least-privilege by design: Tight RBAC, just-in-time access for admin roles, session timeouts, and PAM for break-glass accounts.
- App-layer detections: Alert on abnormal OMS queries (bulk exports, unusual filters, large result sets, or atypical hours/locations).
- Segmentation & egress controls: Strict east-west limits between OMS/CRM/OSS; throttle or queue large data exports; require data-loss prevention (DLP) review for bulk pulls.
- Secret hygiene: Rotate API keys/tokens post-incident; audit service accounts; implement short-lived credentials with automated revocation.
- Customer-facing hardening: Randomize CPE default credentials at manufacture/provisioning; disable remote admin by default; require first-boot password change.
The bottom line
This breach underscores a familiar lesson: credential theft can turn routine back-office tools into high-value data taps. TPG’s early containment and the absence of financial/ID records in the OMS limit immediate harm, but phishing risk will rise as attackers weaponize the exposed contact data. Sustained identity hardening and tighter app-layer controls are essential to stop a repeat.
Sources: Reuters coverage; iiNet media statement and customer advisory. Reutersiinet.net.auiiNet Help
data breaches
Cloudflare Outage Disrupts Global Internet — Company Restores Services After Major Traffic Spike
November 18, 2025 — MAG212NEWS
A significant outage at Cloudflare, one of the world’s leading internet infrastructure providers, caused widespread disruptions across major websites and online services on Tuesday. The incident, which began mid-morning GMT, temporarily affected access to platforms including ChatGPT, X (formerly Twitter), and numerous business, government, and educational services that rely on Cloudflare’s network.
According to Cloudflare, the outage was triggered by a sudden spike in “unusual traffic” flowing into one of its core services. The surge caused internal components to return 500-series error messages, leaving users unable to access services across regions in Europe, the Middle East, Asia, and North America.
Impact Across the Web
Because Cloudflare provides DNS, CDN, DDoS mitigation, and security services for millions of domains — powering an estimated 20% of global web traffic — the outage had swift and wide-reaching effects.
Users reported:
- Website loading failures
- “Internal Server Error” and “Bad Gateway” messages
- Slowdowns on major social platforms
- Inaccessibility of online tools, APIs, and third-party authentication services
The outage also briefly disrupted Cloudflare’s own customer-support portal, highlighting the interconnected nature of the company’s service ecosystem.
Cloudflare’s Response and Restoration
Cloudflare responded within minutes, publishing updates on its official status page and confirming that engineering teams were investigating the anomaly.
The company took the following steps to restore operations:
1. Rapid Detection and Acknowledgement
Cloudflare engineers identified elevated error rates tied to an internal service degradation. Public communications were issued to confirm the outage and reassure customers.
2. Isolating the Affected Systems
To contain the disruption, Cloudflare temporarily disabled or modified specific services in impacted regions. Notably, the company deactivated its WARP secure-connection service for users in London to stabilize network behavior while the fix was deployed.
3. Implementing Targeted Fixes
Technical teams rolled out configuration changes to Cloudflare Access and WARP, which successfully reduced error rates and restored normal traffic flow. Services were gradually re-enabled once systems were verified stable.
4. Ongoing Root-Cause Investigation
While the unusual-traffic spike remains the confirmed trigger, Cloudflare stated that a full internal analysis is underway to determine the exact source and prevent a recurrence.
By early afternoon UTC, Cloudflare confirmed that systems had returned to pre-incident performance levels, and affected services worldwide began functioning normally.
Why This Matters
Tuesday’s outage underscores a critical truth about modern internet architecture: a handful of infrastructure companies underpin a massive portion of global online activity. When one of them experiences instability — even briefly — the ripple effects are immediate and worldwide.
For businesses, schools, governments, and content creators, the incident is a reminder of the importance of:
- Redundant DNS/CDN providers
- Disaster-recovery and failover plans
- Clear communication protocols during service outages
- Vendor-dependency risk assessments
Cloudflare emphasized that no evidence currently points to a cyberattack, though the nature of the traffic spike remains under investigation.
Looking Ahead
As Cloudflare completes its post-incident review, the company is expected to provide a detailed breakdown of the technical root cause and outline steps to harden its infrastructure. Given Cloudflare’s central role in global internet stability, analysts say the findings will be watched closely by governments, cybersecurity professionals, and enterprise clients.
For now, services are restored — but the outage serves as a powerful reminder of how interconnected and vulnerable the global web can be.
data breaches
Cloudflare Outage Analysis: Systemic Failure in Edge Challenge Mechanism Halts Global Traffic
SAN FRANCISCO, CA — A widespread disruption across major internet services, including AI platform ChatGPT and social media giant X (formerly Twitter), has drawn critical attention to the stability of core internet infrastructure. The cause traces back to a major service degradation at Cloudflare, the dominant content delivery network (CDN) and DDoS mitigation provider. Users attempting to access affected sites were met with an opaque, yet telling, error message: “Please unblock challenges.cloudflare.com to proceed.”
This incident was not a simple server crash but a systemic failure within the crucial Web Application Firewall (WAF) and bot management pipeline, resulting in a cascade of HTTP 5xx errors that effectively severed client-server connections for legitimate users.
The Mechanism of Failure: challenges.cloudflare.com
The error message observed globally points directly to a malfunction in Cloudflare’s automated challenge system. The subdomain challenges.cloudflare.com is central to the company’s security and bot defense strategy, acting as an intermediate validation step for traffic suspected of being malicious (bots, scrapers, or DDoS attacks).
This validation typically involves:
- Browser Integrity Check (BIC): A non-invasive test ensuring the client browser is legitimate.
- Managed Challenge: A dynamic, non-interactive proof-of-work check.
- Interactive Challenge (CAPTCHA): A final, user-facing verification mechanism.
In a healthy system, a user passing through Cloudflare’s edge network is either immediately granted access or temporarily routed to this challenge page for verification.
During the outage, however, the Challenge Logic itself appears to have failed at the edge of Cloudflare’s network. When the system was invoked (likely due to high load or a misconfiguration), the expected security response—a functional challenge page—returned an internal server error (a 500-level status code). This meant:
- The Request Loop: Legitimate traffic was correctly flagged for a challenge, but the server hosting the challenge mechanism failed to process or render the page correctly.
- The
HTTP 500Cascade: Instead of displaying the challenge, the Cloudflare edge server returned a “500 Internal Server Error” to the client, sometimes obfuscated by the text prompt to “unblock” the challenges domain. This effectively created a dead end, blocking authenticated users from proceeding to the origin server (e.g., OpenAI’s backend for ChatGPT).
Technical Impact on Global Services
The fallout underscored the concentration risk inherent in modern web architecture. As a reverse proxy, Cloudflare sits between the end-user and the origin server for a vast percentage of the internet.
For services like ChatGPT, which rely heavily on fast, secure, and authenticated API calls and constant data exchange, the WAF failure introduced severe latency and outright connection refusal. A failure in Cloudflare’s global network meant that fundamental features such as DNS resolution, TLS termination, and request routing were compromised, leading to:
- API Timeouts: Applications utilizing Cloudflare’s API for configuration or deployment experienced critical failures.
- Widespread Service Degradation: The systemic 5xx errors at the L7 (Application Layer) caused services to appear “down,” even if the underlying compute resources and databases of the origin servers remained fully operational.
Cloudflare’s official status updates confirmed they were investigating an issue impacting “multiple customers: Widespread 500 errors, Cloudflare Dashboard and API also failing.” While the exact trigger was later traced to an internal platform issue (in some historical Cloudflare incidents, this has been a BGP routing error or a misconfigured firewall rule pushed globally), the user-facing symptom highlighted the fragility of relying on a single third-party for security and content delivery on a global scale.
Mitigation and the Single Point of Failure
While Cloudflare teams worked to roll back configuration changes and isolate the fault domain, the incident renews discussion on the “single point of failure” doctrine. When a critical intermediary layer—responsible for security, routing, and caching—experiences a core logic failure, the entire digital economy resting on it is exposed.
Engineers and site reliability teams are now expected to further scrutinize multi-CDN and multi-cloud strategies, ensuring that critical application traffic paths are not entirely dependent on a single third-party’s edge infrastructure, a practice often challenging due to cost and operational complexity. The “unblock challenges” error serves as a stark reminder of the technical chasm between a user’s browser and the complex, interconnected security apparatus that underpins the modern web.
Dassault Systèmes patches severe vulnerability in Apriso manufacturing software that could let attackers bypass authentication and compromise factories worldwide.
A newly disclosed flaw, tracked as CVE-2025-5086, poses a major security risk to manufacturers using Dassault Systèmes’ DELMIA Apriso platform. The bug could allow unauthenticated attackers to seize control of production environments, prompting urgent patching from the vendor and warnings from cybersecurity experts.
A critical vulnerability in DELMIA Apriso, a manufacturing execution system used by global industries, could let hackers bypass authentication and gain full access to sensitive production data, according to a security advisory published this week.
Dassault Systèmes confirmed the flaw, designated CVE-2025-5086, affects multiple versions of Apriso and scored 9.8 on the CVSS scale, placing it in the “critical” category. Researchers said the issue stems from improper authentication handling that allows remote attackers to execute privileged actions without valid credentials.
The company has released security updates and urged immediate deployment, warning that unpatched systems could become prime targets for industrial espionage or sabotage. The flaw is particularly alarming because Apriso integrates with enterprise resource planning (ERP), supply chain, and industrial control systems, giving attackers a potential foothold in critical infrastructure.
- “This is the kind of vulnerability that keeps CISOs awake at night,” said Maria Lopez, industrial cybersecurity analyst at Kaspersky ICS CERT. “If exploited, it could shut down production lines or manipulate output, creating enormous financial and safety risks.”
- “Manufacturing software has historically lagged behind IT security practices, making these flaws highly attractive to threat actors,” noted James Patel, senior researcher at SANS Institute.
- El Mostafa Ouchen, cybersecurity author, told MAG212News: “This case shows why manufacturing execution systems must adopt zero-trust principles. Attackers know that compromising production software can ripple across supply chains and economies.”
- “We are actively working with customers and partners to ensure systems are secured,” Dassault Systèmes said in a statement. “Patches and mitigations have been released, and we strongly recommend immediate updates.”
Technical Analysis
The flaw resides in Apriso’s authentication module. Improper input validation in login requests allows attackers to bypass session verification, enabling arbitrary code execution with administrative privileges. Successful exploitation could:
- Access or modify production databases.
- Inject malicious instructions into factory automation workflows.
- Escalate attacks into connected ERP and PLM systems.
Mitigations include applying vendor patches, segmenting Apriso servers from external networks, enforcing MFA on supporting infrastructure, and monitoring for abnormal authentication attempts.
Impact & Response
Organizations in automotive, aerospace, and logistics sectors are particularly exposed. Exploited at scale, the vulnerability could cause production delays, supply chain disruptions, and theft of intellectual property. Security teams are advised to scan their environments, apply updates, and coordinate incident response planning.
Background
This disclosure follows a string of high-severity flaws in industrial and operational technology (OT) software, including vulnerabilities in Siemens’ TIA Portal and Rockwell Automation controllers. Experts warn that adversaries—ranging from ransomware gangs to state-sponsored groups—are increasingly focusing on OT targets due to their high-value disruption potential.
Conclusion
The CVE-2025-5086 flaw underscores the urgency for manufacturers to prioritize cybersecurity in factory software. As digital transformation accelerates, securing industrial platforms like Apriso will be critical to ensuring business continuity and protecting global supply chains.
New X Feature Reveals Where Users Really Are — And It’s Already Causing Chaos
Verizon Slashes Jobs in Record-Breaking Layoff — Here’s What We Know
