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...

Coupang

E-Com

loading..
loading..
loading..

Coupang’s Undetected 5 Month Breach Leaves 33.7M Users Exposed

South Korea’s Coupang confirmed a data breach that exposed the names, email addresses, phone numbers, and addresses of 33.7 million customers — the most signifi...

02-Dec-2025
8 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...

A coordinated surge of exploit activity targeting two high-impact WordPress plugin vulnerabilities has put more than 110,000 websites at immediate risk of full compromise. The vulnerabilities — an **unauthenticated Remote Code Execution (RCE)** flaw in **Advanced Custom Fields: Extended (ACF Extended)** and an **unauthenticated administrator-creation exploit** in **King Addons for Elementor** — dramatically escalate the threat surface for WordPress sites across industries. Both flaws are **zero-click**, **no-authentication**, and **weaponized in the wild**, making them among the most critical WordPress threats disclosed this year. ## **1. ACF Extended RCE (100,000+ Sites): A Silent Execution Vector With Server-Level Reach** The vulnerability in **ACF Extended** emerged from a code path inside the plugin’s form preparation routine. A non-privileged actor can inject arbitrary parameters into a function that is eventually passed through PHP's `call_user_func_array()`, enabling the **direct execution of attacker-controlled code on the hosting server**. ### **Technical Breakdown** * Vulnerable versions: **0.9.0.5 → 0.9.1.1** * Attack complexity: **Low**, no authentication required * Exploit vector: **Manipulated input passed to a dynamic function call** * Impact: * Execution of arbitrary PHP * Webshell deployment * Database extraction * Persistent backdoor installation * Privilege escalation via rogue admin creation This flaw effectively collapses the boundary between WordPress and the underlying server, allowing attackers to pivot from web-level access to complete system-level dominance. ### **Threat Intelligence Summary** Analysis of similar code-execution chains shows that adversaries typically follow a predictable pattern: 1. **Initial probe** via automated scanners 2. **Payload injection** through malformed form submission 3. **Webshell deployment** disguised inside media directories 4. **Admin account insertion** as redundancy 5. **Lateral movement** into hosting environment 6. **Monetization stage**, such as cryptojacking, phishing pages, or SEO poisoning Version **0.9.2** patches the flaw, but telemetry indicates that a high percentage of active installations remain outdated. ## **2. King Addons for Elementor: Administrator Takeover Under Active Exploitation** The second threat originates from a privilege-handling failure inside the **King Addons** AJAX registration module. By design, user role assignment should be enforced on the server. Instead, the plugin accepts the `user_role` parameter **directly from the client**, enabling attackers to register themselves as **administrators**. Because the entire operation is executed through `admin-ajax.php`, no authentication is required. ### **Technical Breakdown** * Vulnerable versions: **24.12.92 → 51.1.14** * Fixed version: **51.1.35** * CVSS score: **9.8 Critical** * Attack requirement: **None (unauthenticated)** This flaw provides attackers a **frictionless route to full site control**, including: * Plugin/theme modification * Database access * Arbitrary file uploads * Placement of phishing frameworks * Ransomware staging * Injection of SEO spam across pages ### **Active Exploitation Indicators** Threat groups began abusing the flaw almost immediately after disclosure. Recorded exploit activity includes: * **Tens of thousands of automated POST requests** targeting registration endpoints * Waves of **newly created admin accounts**, often with usernames like `wp-admin-new`, `system-user`, or random strings * Uploads of obfuscated PHP droppers to `/wp-content/uploads/` * Redirect injections funneling traffic to tech-support scams or crypto-fraud sites This vulnerability is already functioning as an entry point in **large-scale botnet campaigns**, indicating its widespread abuse. ## **3. Combined Threat Impact: Systemic Risk to the WordPress Ecosystem** These two vulnerabilities, though distinct in nature, share a dangerous alignment: * **Both allow full compromise with zero authentication.** * **Both integrate cleanly into automated exploit frameworks.** * **Both enable post-exploitation persistence**, making detection challenging. * **Both affect high-usage plugins with weak update hygiene.** In technical terms, these vulnerabilities offer two of the most valuable primitives in exploitation: * **RCE (ACF Extended)** → Control the server * **Privilege escalation (King Addons)** → Control the CMS When used together, they form a **complete compromise chain** capable of collapsing an entire digital infrastructure. This has substantial implications for: * eCommerce storefronts * Membership sites * Marketing funnels * SME corporate websites * Agencies hosting multiple client installations * Managed WordPress service providers ## **4. Risk Modeling: What Attackers Gain From Exploiting These Flaws** ### **High-Value Attack Outcomes** | Attack Goal | Achieved Through | | ---------------------------------------- | ----------------------- | | Full administrative takeover | King Addons | | Server command execution | ACF Extended | | Data theft / DB extraction | Both | | Ransomware payload delivery | ACF Extended | | SEO spam / malicious redirect injections | Both | | Email phishing infrastructure deployment | King Addons | | Botnet node recruitment | ACF Extended (post-RCE) | ### **Operational Use Cases for Attackers** * **Mass infection campaigns** against WordPress clusters * **Cryptomining operations** using server resources * **Malvertising & traffic hijacking networks** * **Credential harvesting (SMTP, DB credentials)** * **Supply-chain poisoning** of themes and plugins stored on compromised sites ## **5. Forensic Indicators Suggesting Compromise** Administrators should immediately investigate if they observe: ### **Indicators of RCE (ACF Extended)** * Unknown PHP files in `/uploads/` or `/wp-includes/` * Sudden file permission changes * CPU spikes (cryptomining behavior) * Suspicious POST traffic to form-related endpoints * Irregular entries in Apache/Nginx logs ### **Indicators of Admin Takeover (King Addons)** * New admin users created without authorization * Requests to `admin-ajax.php?action=register_user` with role manipulation * Modified `.htaccess` or injected JavaScript blocks * Unexpected plugin installations * Redirect loops or injected iframe payloads ## **6. Immediate Remediation Checklist** ### **Patch Immediately** * ACF Extended → **0.9.2+** * King Addons → **51.1.35+** ### **Then Conduct These Steps** 1. Disable vulnerable plugins if patching is delayed. 2. Audit all admin accounts. 3. Change database and wp-admin credentials. 4. Regenerate salts in `wp-config.php`. 5. Scan entire installation for injected PHP. 6. Restore from a trusted backup if compromise is detected. 7. Deploy a Web Application Firewall (WAF). 8. Enforce 2FA and strict role assignments. ## **7. Long-Term Hardening Strategy** To reduce exposure to similar threats: * Limit plugin count to essential, verified extensions. * Use managed update pipelines (e.g., CI/CD for WordPress). * Enforce minimal permissions on file system and database. * Use server-level isolation for multi-tenant hosting environments. * Implement continuous threat monitoring and integrity checks. WordPress doesn’t fail because it’s insecure — it fails because its **plugin ecosystem is porous, fragmented, and inconsistently maintained**. These two vulnerabilities exemplify how quickly a neglected update can escalate into a full-scale compromise. The dual emergence of an RCE flaw and a privilege-escalation flaw in popular WordPress plugins signals a critical moment for the ecosystem. Attackers no longer rely on brute force or credential stuffing — they exploit **logic flaws**, **unsafe developer assumptions**, and **update fatigue**.

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

ShadyPanda

7-year ShadyPanda campaign infected over 4.3 million browsers via malicious Chro...

**In one of the most sustained digital espionage campaigns ever uncovered, over 4.3 million Chrome and Edge users had their browsing activity, passwords, and online identities silently harvested for years by the very browser extensions they trusted.** Dubbed "ShadyPanda" by cybersecurity firm Koi Security, this seven-year campaign exploited a fundamental flaw in the global browser ecosystem, turning routine security updates into a weapon against unsuspecting users. The investigation reveals a patient, sophisticated operation in which attackers first published legitimate extensions, gained coveted "Featured" status in official stores, and then—years later—pushed malicious updates that transformed helpful tools into full-spectrum spyware. As of early December 2025, extensions linked to the campaign, including one with approximately 3 million installations, reportedly remain available on the Microsoft Edge Add-ons store despite public disclosure. ### Patient Digital Heist The ShadyPanda operation didn't hack browsers; it hijacked trust. Its methodology reveals a blueprint for modern digital infiltration: **Phase 1: The Legitimate Front (2018-2023)** Attackers published over 150 benign extensions—primarily wallpaper managers, screenshot tools, and productivity enhancers—to the Chrome Web Store and Microsoft Edge Add-ons store. These passed standard reviews, accumulated millions of users, and some even earned official "Featured" or "Verified" badges, the highest trust signals in browser marketplaces. **Phase 2: The Silent Weaponization (Mid-2024)** The critical turn came through routine, automated updates. Extensions like "Clean Master," with established user bases, received updates containing a sophisticated Remote Code Execution (RCE) framework. This allowed attackers to silently deploy any surveillance payload at will, turning browsers into live-feeds of user activity. **Phase 3: Live Surveillance & Data Harvesting (Ongoing)** At least five extensions on the Edge store, including the massively popular "WeTab" (3 million installs), continue to actively collect: * Complete browsing history and real-time activity * Authentication cookies (enabling account takeover) * Keystrokes and form data (including passwords) * Device fingerprints and location data * Screenshots of browser sessions ### Why It Worked "This campaign exposes the bankruptcy of the 'review-at-submission' model that both Google and Microsoft employ," explains Dr. Elena Vargas, a supply-chain security researcher at MIT. "We treat extensions like trusted applications, but their update mechanism operates like an unguarded backdoor." The central failure is procedural: both major browser stores conduct primary security reviews only when an extension is first submitted. Subsequent updates are largely automated and trusted, creating what security professionals call a "supply-chain attack vector." ShadyPanda simply waited out the initial review period—sometimes for five years—before deploying its malicious payloads. A comparative analysis reveals stark differences in platform response: | Platform | Number of Identified Malicious Extensions | Key Example | Current Status (Dec 2025) | Response Timeframe | | :--- | :--- | :--- | :--- | :--- | | **Chrome Web Store** | 150+ extensions | "Clean Master" (RCE backdoor) | **Removed** post-disclosure | Days after disclosure | | **Microsoft Edge Add-ons** | 5+ active extensions | "WeTab" (3M+ installs) | **Reportedly still available** | No public removal/statement | ### Beyond Numbers While 4.3 million is a staggering figure, the true impact is qualitative. Affected users include: * **Business Professionals**: Whose corporate credentials and internal tool access may have been compromised * **Financial Services Users**: Whose banking sessions and personal finance data were exposed * **Journalists & Activists**: Whose browsing patterns and communications could identify sources or associates * **Healthcare Patients**: Researching sensitive medical conditions through compromised browsers "This isn't just stolen credit cards," notes Marcus Thrane, head of incident response at a global cybersecurity firm. "This is the gradual, comprehensive mapping of digital lives—relationships, interests, fears, and identities—sold to the highest bidder or leveraged for more targeted attacks." ### Commercial Spyware Pipeline Evidence suggests the stolen data feeds a growing commercial surveillance ecosystem. According to leaked threat actor communications analyzed by security firm Unit 221B, browser history datasets from Western users command premium prices in underground forums, often categorized by: * **Professional Value**: IT administrators, developers, and executives * **Interest-Based Targeting**: Political affiliations, health conditions, sexual orientation * **Financial Capacity**: Banking, investment, and luxury goods browsing The extensions themselves appear financially motivated through multiple streams: affiliate fraud (hijacking shopping commissions), direct data sales, and potentially targeted ad injection. ### Regulatory Blind Spot The ShadyPanda campaign operates in a regulatory gray zone. Unlike data breaches where personally identifiable information is stolen from a company's database, this constitutes a distributed, continuous collection directly from user devices. * **GDPR/CCPA Implications**: While these regulations grant users rights over their data, enforcement against anonymous threat actors operating through foreign infrastructure remains nearly impossible. * **Platform Liability**: Current interpretations of Section 230 in the U.S. generally protect platforms from liability for third-party content, potentially including malicious extensions. * **Consumer Protection Gaps**: No mechanism exists for notifying the millions of affected individuals, as there's no responsible entity to coordinate disclosure. ### Beyond Basic Security For organizations and advanced users: 1. **Enterprise Extension Management**: Enterprises should deploy centralized browser management that whitelists only pre-vetted extensions and blocks automatic updates for critical tools. 2. **Network-Level Monitoring**: Unusual traffic patterns from browsers to known malicious servers (identified in Koi's report) should trigger immediate incident response. 3. **Credential Rotation Strategy**: Assume authentication cookies are compromised; implement mandatory re-authentication for sensitive applications. 4. **Browser Segmentation**: Use separate browser profiles or virtual machines for different activities (work, personal, finance, healthcare). ShadyPanda represents more than a large-scale malware campaign; it signals the end of naive trust in the digital tools we use daily. The very mechanisms designed for our protection—automated updates, platform verification badges, centralised app stores—were systematically weaponised against us. The campaign's seven-year success reveals an uncomfortable truth: in today's digital ecosystem, legitimacy is not a permanent state but a temporary condition that invisible actors can revoke at any moment. As browsers become our primary interface to the world—handling everything from email to banking to healthcare—their extension ecosystems represent one of the largest, least-regulated software supply chains on Earth. Until platforms implement continuous behavioral analysis of extensions (monitoring what they *do* after approval, not just what they *claim* to do at submission), and until regulatory frameworks recognize distributed data collection as the systemic threat it represents, the ShadyPanda blueprint will inevitably be replicated. In the architecture of modern digital life, we've discovered that the most convenient doors are also the easiest to leave unlocked—and someone has been walking through them for seven years. The final irony may be this: the extensions promised to enhance our browsing experience. Instead, they turned our browsers into panopticons, proving that in the digital age, the most valuable commodity isn't technology, but the trust we place in it.

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