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

FFF

loading..
loading..
loading..

FFF Data Breach Hits Millions of Fans & Players

The FFF confirms a third major data breach, exposing personal details of players, coaches, and fans. Learn what data was stolen and how to protect yourself from...

29-Nov-2025
6 min read

No content available.

Related Articles

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

BitBucket

GitLab

Over 17,000 sensitive secrets leaked from public GitLab repos, exposing major se...

Based on the research by security engineer Luke Marshall, who uncovered over 6,000 live secrets in public Bitbucket repositories, the narrative is clear: established enterprise platforms are an overlooked goldmine for attackers, harboring long-forgotten, highly impactful credentials. This article reconstructs his investigation to provide a technically detailed account of the findings and their broader implications for cloud security. ### Why Bitbucket? While much of the security community's attention has been on platforms like [GitHub](https://www.secureblink.com/cyber-security-news/20-000-projects-impacted-coinbase-targeted-in-massive-git-hub-attack) and [GitLab](https://www.secureblink.com/cyber-security-news/red-hat-breach-exposes-customer-network-blueprints), [Bitbucket](https://www.secureblink.com/cyber-security-news/bitbucket-outage-exposes-fragile-backbone-of-software-development) has been a compelling target for investigation. In operation since 2008 and owned by Atlassian, it hosts code for thousands of enterprises. Its appeal to security researchers stemmed from two key factors: the inherent nature of Git, which can bury secrets deep within commit history, and the fact that it has not received the same level of scrutiny from security tooling and researchers as its competitors. This combination suggested a potential trove of undiscovered exposed credentials. ### Engineering a Large-Scale Scan To accurately assess the scale of the problem, the goal was to scan every public Bitbucket Cloud repository—a total of 2,636,562 as of the initial [research](https://trufflesecurity.com/blog/scanning-2-6-million-public-bitbucket-cloud-repositories-for-secrets) date. Handling this volume required a robust and scalable automation strategy. The solution was a serverless architecture built on AWS, chosen for its ability to handle the massive workload efficiently. The process involved two core components : 1. A local Python script that fed all 2.6 million repository names into an AWS Simple Queue Service (SQS) queue, creating a durable and managed task list . 2. An AWS Lambda function, triggered by the queue, that performed the actual scanning using TruffleHog with a concurrency of 300. This setup ensured no repository was scanned twice and provided fault tolerance; if any part of the process failed, it could seamlessly resume without losing progress. This architecture enabled the scanning of all 2.6 million repositories over a single weekend . ### A Legacy of Exposure The scan yielded **6,212 verified live secrets** . The [analysis](https://trufflesecurity.com/blog/scanning-5-6-million-public-gitlab-repositories-for-secrets) of these secrets revealed several alarming trends that challenge conventional security assumptions. The table below breaks down the leaked credentials by service and file type, showing where and how these exposures occurred : | **Secrets by Cloud Service** | **Secrets by File Extension** | | :--- | :--- | | • **GCP**: 977 secrets<br>• **AWS IAM**: High-impact<br>• **SendGrid**: High-impact<br>• **MongoDB**: High-impact<br>• **OpenAI**: High-impact<br>• **Atlassian**: 247 secrets<br>• **Azure Storage**: High-impact<br>• **Stripe, Slack, Twilio**: High-impact | • **JSON**: Most common<br>• **PHP**: 4th most common<br>• **Python (.py)**: Large footprint<br>• **JavaScript (.js)**: Large footprint | One of the most surprising findings was the age of the live credentials. The research uncovered secrets that had been sitting exposed for years, including a live AWS key committed **12 years ago**, in June 2013. The research graph shows a consistent average of 600-700 live secrets exposed each year between 2018 and 2024. This indicates that once a secret is committed, it often remains alive and undiscovered indefinitely. A particularly ironic finding was the disproportionately high number of exposed credentials for Atlassian's own products, including Jira, Bitbucket, and Opsgenie. In total, 247 valid Atlassian credentials were discovered, a volume much higher than seen in similar scans of other software ecosystems . ### Defense and Response The findings underscore a critical need for robust defensive measures. To address these risks, Bitbucket has integrated a native **secret scanning feature**. This scanner checks new commits for over 800 patterns of known secret types and alerts authors and committers via email when a potential leak is detected. The system is customizable, allowing admins to define their own regular expression (regex) patterns for proprietary secret formats and create allow lists to reduce false positives. However, technology alone is not enough. The research also triggered a vital security response. Alongside the TruffleHog team, the researcher participated in a responsible disclosure process that led to the revocation of thousands of live secrets. Furthermore, 11 critical P1 vulnerabilities were submitted to bug bounty programs, and over 50 organizations were notified of their exposed secrets. ### Key Takeaways for Security Teams This investigation offers crucial insights for the security community: * **Assess Your Entire Ecosystem**: Security efforts must include all code hosting platforms in use, not just the most popular ones. Overlooked, legacy systems can present significant risk . * **Secrets Have a Long Lifespan**: The discovery of a 12-year-old live AWS key proves that "secrets don't rot." Credentials exposed in the past remain a threat until they are actively found and revoked. **Assume Compromise and Rotate**: If a secret is discovered in a repository, treat it as compromised. Simply removing it from the git history is insufficient, as the commit may exist in forks, clones, or other branches. The only safe response is to **immediately revoke and rotate the credential**. **Leverage Available Tools**: Proactively use secret-scanning tools like TruffleHog or native features on platforms like Bitbucket to continuously monitor for accidental exposures, both in real-time and through historical analysis.

loading..   28-Nov-2025
loading..   5 min read