On May 22, 2026, the qilin ransomware group added Semgrep to its public leak site, claiming that internal files had been exfiltrated from the code-security company during a ransomware attack. The listing affects anyone whose information was stored in those internal systems, including current and former employees, customers whose support tickets or contracts were saved internally, and partners whose details appeared in the compromised files.
Already exposed?
You can’t unleak data. You can take away what it’s worth.
A leaked record is where it starts, not where it ends. What turns it into your front door is the look-up sites publishing your address beside your name — and those are what an AI reads when somebody asks about you. The free scan shows you both. We write to 580 companies.
See what is exposed about you — free scan →Watch Semgrep
Get alerted the next time Semgrep files a breach with any US regulator — the filing, dated and sourced. A free single-company slice of Signals; no account needed.
We’ll email you only about Semgrep’s future breach filings and how to watch a whole vendor list — not general marketing. Unsubscribe any time.
Watching your whole vendor list (50 to 500 companies, by tier) is GalaxyWarden Signals.
What Public Reporting Shows
Public reporting indicates that qilin operators gained access to Semgrep’s network, encrypted systems, and then exfiltrated a volume of internal documents before publishing a sample on their leak portal. The exact number of people impacted remains unknown because the company has not released a formal count of records or individuals. Available reporting describes the exposed material as internal files rather than a structured database of customer credentials. No public evidence has surfaced showing that customer passwords, payment card data, or Social Security numbers were taken, but the breach still places sensitive business correspondence, contracts, and contact lists at risk of public release if ransom demands are not met.
Why This Matters for You and Your Family
When a security vendor like Semgrep is breached, the ripple effects reach ordinary users. Your email address, support history, or licensing details may have been stored in the very files now held by attackers. Internal files exfiltrated often contain notes that link personal or family email accounts to specific software licenses, making it easier for criminals to target you with follow-on phishing or account takeover attempts. For families, this can mean a child’s school email used for a parent’s work trial suddenly becomes part of a larger data set that criminals can weaponize. The breach reminds us that even companies we trust to protect our code and data can become gateways to personal exposure.
The Doxxing and Identity-Chain Implications
Stolen internal files frequently contain more than names and emails. They can include support tickets, chat logs, IP addresses, and references to third-party accounts. Attackers routinely combine these fragments with data from earlier breaches to build an identity chain that links your work email to personal accounts, phone numbers, and even children’s online profiles. Once that chain exists, a single leaked support conversation can lead to doxxing, SIM-swapping attempts, or harassment campaigns. Credential leaks like this one also cascade into gaming account takeovers when family members reuse passwords across work tools and entertainment platforms.