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

Trickbot

loading..
loading..
loading..

Malicious Software Emails Sent To Trickbot From Hacked Subway System

Subway UK has revealed recently that their hacked system was responsible for sending software-laden fake emails to customers previously

17-Dec-2020
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...

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

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