company logo

Product

Our Product

We are Reshaping the way Developers find and fix vulnerabilities before they get exploited.

Solutions

By Industry

BFSI

Healthcare

Education

IT & Telecom

Government

By Role

CISO

Application Security Engineer

DevsecOps Engineer

IT Manager

Resources

Resource Library

Get actionable insight straight from our threat Intel lab to keep you informed about the ever-changing Threat landscape.

Subscribe to Our Weekly Threat Digest

Company

Contact Us

Have queries, feedback or prospects? Get in touch and we shall be with you shortly.

loading..
loading..
loading..
Loading...

Apple

loading..
loading..
loading..

Apple releases patches to fix flaws risking billions of devices

Apple has released patches for iOS, macOS, watchOS, and Safari to correct a security flaw that could permit hackers to execute arbitrary code on devices

12-Mar-2021
2 min read

No content available.

Related Articles

loading..

Mixpanel

A hidden Mixpanel breach exposes sensitive user analytics and raises serious que...

Mixpanel, one of the most widely embedded product analytics platforms in the SaaS ecosystem, confirmed a security incident that has rapidly escalated into a broader industry concern. What initially appeared to be a limited intrusion has evolved into a significant exposure event, revealing how deeply analytics services are embedded in modern architectures — and how vulnerable the ecosystem becomes when a telemetry provider is compromised. An unauthorized actor gained access to part of Mixpanel’s environment and exported a dataset containing identifiable analytics information. While the company stated that no passwords or payment data were exposed, the leaked set included names, emails, IP-derived geolocation, device metadata, and behavioral telemetry. In theory, this is “low-sensitivity.” In practice, it is the raw material for targeted phishing, identity profiling, and social-engineering attacks — a pattern well documented by organizations such as **[CISA](https://www.cisa.gov)** and **[ENISA](https://www.enisa.europa.eu/topics/csirt-cert-services)**. ## **A Breach Rooted in Human Error — and Predictable Attack Patterns** The attack was triggered by a smishing message that deceived an internal user. Smishing has become a primary initial-access vector, with global trends highlighted by the **[Verizon’s Data Breach Investigations Report](https://www.verizon.com/business/resources/reports/dbir/)**, which shows social engineering as the leading attack category for enterprise compromise. Once the attacker obtained session access, they used Mixpanel’s analytics export functionality to pull a curated dataset. This was not a chaotic grab; the extraction showed precision, aligning with the attacker behavior patterns described in **[Microsoft’s Threat Intelligence reports](https://www.microsoft.com/en-us/security/business/microsoft-threat-intelligence)** — attackers increasingly prefer targeted reconnaissance over noisy exfiltration. Mixpanel revoked access, rotated credentials, and engaged incident-response specialists, following industry incident-handling practices such as those outlined in **[NIST’s Computer Security Incident Handling Guide](https://csrc.nist.gov/publications/detail/sp/800-61/rev-2/final)**. But delays in customer notification highlight a persistent problem across the SaaS supply chain: the absence of real-time transparency when a vendor is breached. ## **Why “Low-Sensitivity” Telemetry is a Myth** Telemetry pipelines now collect a blend of identifiers, metadata, and event-level behavior. Individually, none of these fields seem dangerous. Together, they form high-resolution attack intelligence. * **Email address + device type** enables tailored phishing templates. * **Location + browsing environment** helps adversaries mimic trusted service alerts. * **Behavioral event logs** provide timing patterns for credential-harvesting attacks. Threat groups have repeatedly used such contextual profiling in major campaigns documented by **[Mandiant](https://www.mandiant.com/resources)** and **[CrowdStrike](https://www.crowdstrike.com/threat-intelligence/)**. The broader security community has long warned that metadata — not just passwords or financial data — fuels sophisticated intrusion workflows. The Mixpanel breach validates that position. ## **OpenAI’s Containment Strategy Shows How Critical This Exposure Is** OpenAI, one of Mixpanel’s high-visibility customers, immediately severed all telemetry integrations once notified. Although the leaked data concerned mainly API-level analytics rather than ChatGPT logs or credentials, OpenAI treated the situation as a material security incident. This aligns with best practices emphasized by **[NIST’s Zero Trust Architecture](https://www.nist.gov/publications/zero-trust-architecture)**: assume breach, compartmentalize, and remove unnecessary trust paths. Telemetry providers are deeply embedded in core workflows — and once compromised, they become a propagation vector for further attacks. ## **A Supply Chain Built on Implicit Trust** The Mixpanel exposure points to wider systemic issues. ### **1. Overprivileged Telemetry Pipelines** Many organizations give analytics vendors unrestricted event access. Research by **[OWASP](https://owasp.org/www-project-top-ten/)** repeatedly highlights excessive data collection as a critical weakness. ### **2. Export Functions With Weak Guardrails** Bulk data export should require multi-party approval or privileged workflows, a principle supported by frameworks like **[ISO 27001](https://www.iso.org/isoiec-27001-information-security.html)**. Yet many SaaS analytics dashboards allow single-click extraction of large datasets. ### **3. Insufficient Monitoring of Vendor Activity** Organizations often fail to track what vendors are accessing or exporting — a risk repeatedly stressed in **[Gartner’s Third-Party Risk Insights](https://www.gartner.com/en)**. ### **4. Vulnerable Notification Windows** Delays in vendor breach disclosure cut into the critical window where organizations can reset credentials or warn users. This is a recurring issue seen across recent supply-chain attacks documented by **[SANS ICS reports](https://www.sans.org/ics/)**. ## **What Organizations Must Do Immediately** To prevent analytics-driven supply-chain breaches, enterprises must adopt stricter governance: ### **Audit Telemetry Streams** Follow data-minimization principles aligned with **[GDPR Article 5](https://gdpr-info.eu/art-5-gdpr/)** and remove unnecessary identifiers such as emails or full IPs. ### **Require Phishing-Resistant MFA** Adopt hardware-key or certificate-based authentication as recommended by **[FIDO Alliance](https://fidoalliance.org/)** for any admin-facing analytics system. ### **Restrict Export Capabilities** Bulk exports should: * require elevated roles, * be logged immutably, * support anomaly alerts, * and use approval workflows similar to **[SOC 2 controls](https://www.aicpa-cima.com/resources/article/aicpasocsuite)**. ### **Continuously Monitor Vendor Behavior** Organizations should require vendors to provide access logs, export logs, and anomaly alerts, aligning with best practices outlined by **[CSA’s Cloud Controls Matrix](https://cloudsecurityalliance.org/research/cloud-controls-matrix)**. ### **Rebuild Vendor Contracts** Contracts should enforce: * strict least-privilege data handling, * data residency guarantees, * breach notification SLAs, * and external security audits guided by **[NIST 800-53](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final)**. Analytics platforms were once considered harmless reporting tools. Today, they function as shadow identity providers, session observers, and behavioral data aggregators — precisely the kind of systems adversaries want to compromise. Unless companies adopt rigorous telemetry governance, breaches like this will become routine.

loading..   04-Dec-2025
loading..   5 min read
loading..

Wordpress

Critical WordPress Plugin Flaws Threaten Tens of Thousands of Sites...

Security researchers have recently uncovered two severe vulnerabilities affecting popular WordPress plugins — one enabling remote code execution (RCE) and the other facilitating full administrative takeover. The flaws lie in widely used add-ons: Advanced Custom Fields: Extended (ACF Extended) and King Addons for Elementor. Immediate action is strongly recommended for any site running these plugins. ## Remote Code Execution in ACF Extended — 100,000+ Sites at Risk A major security issue has been identified in ACF Extended versions 0.9.0.5 through 0.9.1.1. The vulnerability, tracked as CVE-2025-13486, allows unauthenticated attackers to execute arbitrary code on the server simply by sending a crafted request. ([Wordfence][1]) * The root cause is unsafe input handling: user-supplied data is passed into a `call_user_func_array()` invocation without adequate sanitization or validation. ([Wordfence][1]) * This makes it possible to drop backdoors or arbitrary files onto the server, or to escalate privileges — for instance by creating new administrative accounts. ([Wordfence][1]) * Given ACF Extended’s widespread use, more than 100,000 WordPress installations are potentially vulnerable. ([Wordfence][1]) The maintainers responded quickly: a fixed version — 0.9.2 — was released on November 21, 2025. ([businessabc.net][2]) For added defense, the security firm Wordfence rolled out a firewall rule for its Premium, Care, and Response customers on November 20, 2025. ([businessabc.net][2]) **Recommendation:** If your site uses ACF Extended, update to version 0.9.2 (or later) immediately. If an immediate upgrade isn’t feasible, consider disabling the plugin until patched. --- ## Privilege Escalation in King Addons — Full Site Takeover in Active Exploits In a separate but equally serious alert, Wordfence disclosed a critical vulnerability in King Addons for Elementor, tagged CVE-2025-8489. This bug allows unauthenticated attackers to create new administrator accounts by manipulating the user role during registration. ([Wordfence][3]) ### Technical Details * The flaw is located in the plugin’s AJAX registration handler (function `handle_register_ajax()`). Rather than enforcing a safe default role (like “subscriber”), the code accepts a `user_role` parameter supplied by the user — even “administrator.” ([Security Online][4]) * An attacker can exploit this by sending a crafted POST request to `/wp-admin/admin-ajax.php`, setting `user_role=administrator`. No prior access or authentication is required. ([Security Online][4]) * Successfully created admin accounts give full control over the site — allowing malicious file uploads, content tampering, phishing/redirection, spam injection, or other malicious actions. ([The Hacker News][5]) ### Scope and Exploitation * King Addons for Elementor is active on more than 10,000 WordPress sites. ([Wordfence][3]) * The vulnerability carries a CVSS severity of 9.8 (Critical). ([The Hacker News][5]) * A patched version — 51.1.35 — was released on September 25, 2025. ([The Hacker News][5]) * According to Wordfence telemetry, exploitation began almost immediately — starting October 31, 2025 — with attacks quickly escalating thereafter. ([Wordfence][3]) * So far, more than 48,400 exploit attempts have been blocked by Wordfence. Top offending IP addresses include 45.61.157.120 (≈28,900 attempts) and 2602:fa59:3:424::1 (≈16,900 attempts), among others. ([Security Online][4]) --- ## Implications for WordPress Site Owners Between these two vulnerabilities, the risk to WordPress sites in December 2025 is exceptionally high. Both flaws require **no authentication** and allow deep compromise: * The ACF Extended bug enables remote code execution — letting attackers run arbitrary server-side code. * The King Addons flaw enables full admin takeover, allowing modifications to site structure, content, and backdoor installation. Given their severity and ease of exploitation, these are not merely theoretical — both are being actively weaponized. --- ## Recommended Actions — What You Should Do Right Now 1. **Audit your WordPress installation.** Check if you are using ACF Extended (versions 0.9.0.5–0.9.1.1) or King Addons for Elementor (pre-51.1.35). 2. **Update immediately** — ACF Extended to 0.9.2 or later; King Addons to 51.1.35 (or newer). 3. **If patching is not possible right away, disable the plugins until patched.** 4. **Review user accounts** — look for recently created administrator accounts, especially around late October to early December 2025. 5. **Scan for malicious files** — check for new or modified files in uploads, themes, and plugin directories, especially PHP files or strange backdoors. 6. **Harden WordPress installation** — implement a Web Application Firewall (WAF); enforce strong passwords; disable registration if not needed; restrict plugin use to necessary ones only. --- ## Why This Matters — The Larger Picture These incidents highlight the persistent risk posed by third-party WordPress plugins — especially ones that handle user input, registration, uploads, or dynamic features. Even a single vulnerable plugin can compromise an entire site. The speed — from disclosure to widespread exploitation within a day — underscores the urgency for site owners to keep plugins updated, maintain vigilance, and adopt a defence-in-depth posture (firewalls, monitoring, account audits, backups). In the current climate, such vulnerabilities are no longer “edge cases” — they represent a critical systemic threat to WordPress infrastructure everywhere. --- If you like, I can also produce a short “checklist for admins” version of this — a minimal, copy-paste guide summarizing exactly what to do, step by step. Want me to build one for you now? * [bleepingcomputer.com](https://www.bleepingcomputer.com/news/security/critical-flaw-in-wordpress-add-on-for-elementor-exploited-in-attacks/?utm_source=chatgpt.com) * [techradar.com](https://www.techradar.com/pro/security/another-major-wordpress-add-on-security-flaw-could-affect-10-000-sites-find-out-if-youre-affected?utm_source=chatgpt.com) [1]: https://www.wordfence.com/blog/2025/12/100000-wordpress-sites-affected-by-remote-code-execution-vulnerability-in-advanced-custom-fields-extended-wordpress-plugin/?utm_source=chatgpt.com "100000 WordPress Sites Affected by Remote Code ..." [2]: https://businessabc.net/over-100-000-word-press-sites-affected-by-remote-code-execution-vulnerability-in-popular-plugin?utm_source=chatgpt.com "Over 100000 WordPress Sites Affected by Remote Code ..." [3]: https://www.wordfence.com/blog/2025/12/attackers-actively-exploiting-critical-vulnerability-in-king-addons-for-elementor-plugin/?utm_source=chatgpt.com "Attackers Actively Exploiting Critical Vulnerability in King ..." [4]: https://securityonline.info/critical-elementor-plugin-flaw-cve-2025-8489-cvss-9-8-under-active-exploitation-allows-unauthenticated-admin-takeover/?utm_source=chatgpt.com "Critical Elementor Plugin Flaw (CVE-2025-8489, CVSS 9.8 ..." [5]: https://thehackernews.com/2025/12/wordpress-king-addons-flaw-under-active.html?utm_source=chatgpt.com "WordPress King Addons Flaw Under Active Attack Lets ..."

loading..   04-Dec-2025
loading..   6 min read
loading..

E-Com

Coupang

South Korea’s Coupang confirmed a data breach that exposed the names, email addr...

South Korean e-commerce giant **Coupang** has confirmed a massive data breach that exposed the personal information of about **33.7 million customer accounts**, in what officials are calling **South Korea’s worst data leak in more than a decade**. The incident, disclosed publicly on **December 1, 2025**, involves a **five-month intrusion window** that remained undetected until mid-November and has triggered criminal investigations, regulatory scrutiny, political backlash and a sharp hit to Coupang’s market value. ## Breach at a Glance: 5-Month Window, 33.7M Accounts, Overseas Servers Coupang first spotted something was wrong on **November 18**, when it detected unauthorised access affecting about **4,500 user accounts**. A deeper forensic review then revealed that the attacker had, in fact, accessed data tied to roughly **33.7 million customers in South Korea**. Key timeline details: * **Initial unauthorized access:** believed to have begun on **June 24, 2025** * **Infrastructure:** attack traffic routed via **overseas servers**, complicating attribution * **Discovery date:** **November 18, 2025**, after anomalous account activity * **Public disclosure:** weekend of **November 30 – December 1, 2025** The breach window of nearly **five months** is central to both regulatory and political criticism, with President **Lee Jae-myung** calling it “astonishing” that the company failed to recognise the breach for so long. ## What Was Exposed Coupang has confirmed that the attacker accessed a large corpus of customer identity and contact data: * **Full names** * **Email addresses** * **Mobile / phone numbers** * **Shipping and home addresses** * **Portions of order history** (items ordered, related metadata) Equally important is what Coupang says **was not** compromised: * Payment card numbers * Other payment information * Login credentials and account passwords The company maintains that **financial data and authentication passwords remain secure**. However, from a security risk perspective, this still represents a **high-value identity dataset**. Combined names, phone numbers, addresses and order patterns are extremely useful for: * Highly personalized **phishing campaigns** that reference real purchases * **Smishing** (SMS phishing) that impersonates delivery or refund workflows * Social engineering for **account takeover** on other platforms * Targeted **fraud and scam operations** using detailed personal profiles For context, the number of impacted accounts (≈33.7M) exceeds Coupang’s reported **24.7 million active users**, which means dormant or less active accounts were also caught in the exposure. ## How the Attack Worked While full technical details are still emerging, early statements by officials and Coupang executives outline a clear, high-risk pattern: * Investigators believe the attacker used a **stolen private encryption key** to authenticate into Coupang’s systems. * The prime suspect is reportedly a **former Chinese Coupang engineer** who allegedly retained or misused access post-employment. From a security architecture perspective, this suggests several breakdowns: 1. **Key Management & Protection** * A private encryption key used for authentication should be tightly controlled, rotated and stored in hardened key-management systems (HSMs or equivalent). * Successful abuse of such a key indicates either inadequate **key custody** or poor **rotation and revocation** practices after staff departures. 2. **Offboarding & Privileged Identity Management (PIM)** * The involvement of a former employee points to **gaps in access revocation** and privileged identity deprovisioning. * Mature organizations enforce **zero-standing privilege**, strict offboarding checklists and real-time revocation of all keys and tokens. 3. **Network & Data Segmentation** * The ability to pull data at the scale of tens of millions of accounts suggests insufficient **segmentation between customer PI data stores and broader infrastructure**, allowing wide data access once initial credentials were validated. 4. **Behavioral & Anomaly Detection** * A five-month detection lag indicates that **user and entity behavior analytics (UEBA)** and **access pattern anomaly detection** were either absent or ineffective. * Access from overseas servers over a long period, combined with large-volume data queries, should normally trigger alerts in a mature SOC. Put simply: this appears to be a classic **insider-enabled breach** amplified by **weak key and identity governance** and **late-stage detection**. ## Coupang’s Response: Containment, External Forensics and Public Apology Once the incident was detected, Coupang says it took several immediate actions: * **Blocked the unauthorized access route** used via overseas servers * **Strengthened internal monitoring** of access and data flows * **Retained an independent security firm** to support forensics and remediation * **Reported the incident** to key South Korean authorities, including: * Korea Internet & Security Agency (**KISA**) * Personal Information Protection Commission (**PIPC**) * National Police Agency CEO **Park Dae-jun** published a formal apology on Coupang’s website, expressing regret for the incident and pledging full cooperation with investigators and regulators. Despite the apology, the company is facing questions not just about how the breach occurred, but why a platform of its scale lacked the telemetry and controls to contain it sooner. ## Regulatory and Political Fallout: Toward Trillion-Won Penalties The breach has rapidly escalated into a **national policy issue**. * President **Lee Jae-myung** has ordered **swift action to penalize those responsible**, calling for a review of **higher fines and punitive damages** for corporate data-protection failures. * Current law allows penalties up to **3% of annual revenue**. For Coupang, that could mean potential fines exceeding **₩1 trillion** (about **USD 680 million**) in extreme scenarios. * The administration has framed personal data as a **“key asset in the age of AI and digitalization”**, arguing that corporate negligence in this area can no longer be tolerated as a cost of doing business. Regulators are examining whether Coupang violated South Korea’s **personal information protection rules**, particularly around: * Timely detection and disclosure of breaches * Adequate technical safeguards for large-scale PI datasets * Secure handling of encryption keys and access tokens * Offboarding and residual access controls for former employees The combination of **record scale**, **extended exposure window** and **insider indications** makes this case a prime candidate for setting **new precedent** on penalties and compliance expectations in South Korea’s tech sector. ## Market Impact: Stock Slide, Litigation Risk and Trust Deficit The market response has been swift: * Coupang’s **New York–listed stock** dropped around **5–9%** following disclosure, erasing part of the gains it had accumulated earlier in 2025. Beyond immediate price movement, the breach creates several medium-term risks: 1. **Class-Action Lawsuits** * Reports indicate **10,000+ customers** are considering or preparing to join class-action efforts, often seeking at least **₩100,000 per person** in damages. 2. **Higher Cybersecurity and Compliance Spend** * Coupang will likely be forced to increase investments in: significantly * Identity & access management (IAM, PIM, PAM) * Key management and HSM infrastructure * SOC modernization and UEBA tooling * This will pressure margins and may be closely scrutinized by investors during upcoming earnings cycles. 3. **Reputational Damage and Churn** * Trust is central in e-commerce. A breach of this magnitude can: * Increase account deletion and opt-out rates * Reduce order frequency from security-conscious customers * Strengthen competitors who position themselves as “more secure” alternatives ## Coupang’s History of Repeated Data Incidents TechCrunch notes this latest breach arrives on top of **a string of prior incidents** involving Coupang’s systems. Past issues include: * Data leaks between **2020 and 2021** affecting customers and delivery drivers * A **December 2023** incident in which its seller management system exposed the personal information of more than **22,000 customers** This pattern reinforces a key concern for regulators and customers: Coupang’s **security maturity and governance frameworks** have not scaled at the same pace as its **explosive e-commerce growth** in South Korea, Japan, and Taiwan. While Coupang says there is currently **no evidence that Coupang Taiwan or Rocket Now customer data** was affected by the current breach, the company’s multi-market footprint raises the stakes for **cross-border data governance and cloud security posture management**. Any large consumer platform operating in or adjacent to South Korea will be expected to **prove** that lessons from this breach have been internalised. ## Where This Leaves Coupang — and the Region Coupang is often called **“the Amazon of South Korea”**, and this incident demonstrates what happens when massive scale meets imperfect security governance. In the short term, the company faces: * Regulatory investigations * Possible record fines * Class-action lawsuits * A reputational repair challenge that will take sustained transparency and investment In the longer term, this breach is likely to become a **reference case** in Asian cybersecurity: * For lawmakers: a catalyst for **tougher personal-data regulation** * For enterprises: a benchmark for **what not to do** in key management and off-boarding * For users: a reminder that **non-financial personal data still carries real-world risk** If Coupang can demonstrate a credible end-to-end overhaul of its **identity, access and detection stack**, it may eventually turn this crisis into a security-maturity inflexion point. But for now, the incident stands as a stark warning: in modern e-commerce, scale without security is a systemic liability, not an advantage.

loading..   02-Dec-2025
loading..   8 min read