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/CTO

DevOps Engineer

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

VEESE

loading..
loading..
loading..

Chinese Hackers Breach Belgium’s Top Security Service in Major Espionage

Chinese hackers breach Belgium’s top security agency, stealing sensitive data in a major cyber espionage attack

28-Feb-2025
5 min read

No content available.

Related Articles

loading..

LLM

AWS

API

Learn how 12,000 valid API keys and passwords were discovered in the Common Craw...

A massive trove of nearly 12,000 valid API keys and passwords has been uncovered in the Common Crawl repository—an enormous open-source archive used extensively to train large language models (LLMs). This alarming discovery underscores a systemic risk that could be feeding vulnerabilities directly into AI projects at major tech companies. ### Common Crawl’s Global Footprint Common Crawl has, for over a decade, offered petabytes of freely accessible web data. Because it’s so vast, many AI developers—potentially including those behind models at OpenAI, DeepSeek, Google, Meta, Anthropic, and Stability—rely on these archives to build and refine powerful language models. ### Valid Secrets Hiding in Plain Sight Researchers at Truffle Security analyzed 2.67 billion web pages (about 400 terabytes of data) from the December 2024 Common Crawl archive. Their tool, TruffleHog, flagged a staggering **11,908 secrets** that proved **fully functional**—including AWS root keys, MailChimp API keys, Slack webhooks, and more. **Key Findings** - **AWS Root Keys:** Some were exposed directly in front-end code, granting unrestricted access to cloud resources. - **MailChimp Keys:** At least 1,500 were hardcoded in HTML or JavaScript, opening the door to phishing campaigns and brand impersonation. - **WalkScore API Key:** One key alone appeared **57,029 times** across **1,871 subdomains**, illustrating the scope of credential reuse. - **Slack Webhooks:** One single webpage revealed **17 unique** Slack webhook URLs, which attackers could exploit to post messages or infiltrate private channels. ### Why AI Training Data is at Risk Although LLM training typically involves **data-cleaning and filtering** to remove sensitive or redundant information, no process is perfect. The sheer volume of data means **leaked credentials** can slip through, effectively teaching AI systems to regurgitate or even reference them. This threatens the security of the compromised services and raises major concerns about the **ethical and legal implications** of using publicly scraped data for training. ### Consequences of Hardcoded Credentials By embedding keys into front-end files, developers inadvertently grant anyone scanning the web ready access to powerful backend systems. Attackers could exploit these credentials to: - **Spin up malicious cloud infrastructure** using stolen AWS resources - **Launch phishing campaigns** or spam messages via legitimate MailChimp accounts - **Infiltrate private Communication channels** by abusing Slack webhooks - **Exfiltrate sensitive data** from compromised servers ### Mitigation and Lessons Learned Truffle Security collaborated with impacted vendors to rotate or revoke thousands of compromised keys. Still, this incident highlights the urgent need for stronger developer practices, especially as AI continues to devour terabytes of public data. Critical steps include: 1. **Never hardcode secrets** in front-end files—use environment variables or secure vaults. 2. **Routinely scan codebases** with specialized tools (like TruffleHog) to detect exposed credentials. 3. **Implement robust rotation policies** so that any discovered key can be rapidly invalidated. 4. **Strengthen AI data preprocessing** to better identify and strip out sensitive information before training.

loading..   03-Mar-2025
loading..   3 min read
loading..

Lee

Qilin ransomware gang has claimed responsibility for the attack at Lee Enterpris...

The Qilin ransomware gang has claimed responsibility for the attack at Lee Enterprises that disrupted operations on February 3, leaking samples of data they claim was stolen from the company. The threat actors have now threatened to leak all the allegedly stolen data on March 5, 2025, unless a ransom demand is paid. Lee Enterprises is a US-based media company that owns and operates over 77 daily newspapers, 350 publications, digital media platforms, and marketing services. The company's primary focus is local news and advertising, with its digital audience reaches tens of millions monthly. In a filing with the U.S. Securities and Exchange Commission (SEC) earlier this month, the company disclosed that it had suffered a cyberattack on February 3, 2025, causing significant operational disruptions. learned that the outage caused significant problems, such as losing access to internal systems and cloud storage, and corporate VPNs not working. A week later, Lee Enterprises submitted a new filing with the SEC that specified that the hackers "encrypted critical applications and exfiltrated certain files," indicating they got hit by ransomware. Today, Qilin ransomware added Lee Enterprises to its dark web extortion site, sharing samples of the allegedly stolen data, including government ID scans, non-disclosure agreements, financial spreadsheets, contracts/agreements, and other confidential documents allegedly stolen from the firm. Qilin ransomware threatens Lee Enterprises with data leak Qilin ransomware threatens Lee Enterprises with data leak Source: BleepingComputer The ransomware actors claimed to have stolen 120,000 files totaling 350GB in size and threatened to release it all on March 5. BleepingComputer contacted Lee Enterprises to learn if the stolen data belonged to them, but a comment wasn't immediately available. Qilin ransomware evolution Qilin is not one of the most prolific ransomware gangs but has come a long way since it launched in August 2022 under the name "Agenda." Over the years that followed, the cybercriminals claimed hundreds of victims, with some notable cases including automotive giant Yangfeng, Australia's Court Services Victoria, and several major NHS hospitals in London. In terms of its technical evolution, Qilin introduced a Linux (VMware ESXi) variant in December 2023, started deploying a custom Chrome credentials stealer in August 2024, and introduced a Rust-based data locker with stronger encryption and better evasion last October. Last year, Microsoft published a report stating that the notorious members of the 'Scattered Spider' hacker collective had begun to use Qilin ransomware in attacks.

loading..   28-Feb-2025
loading..   3 min read
loading..

SSNExposure

A data breach at DISA Global Solutions exposes sensitive info of 3.3 million ind...

DISA Global Solutions, a leading U.S.-based provider of employee screening services, has reported a significant data breach impacting over **3.3 million individuals**. This breach compromises sensitive personal data, raising concerns regarding the security practices of a major player in the employee screening and compliance sector. --- ### **Incident Discovery:** On **April 22, 2024**, DISA Global Solutions filed an official report with **Maine’s Attorney General** confirming that a **cyber incident** had affected a "limited portion" of its internal network. This breach occurred on **February 9, 2024**, and went undetected for more than two months, compromising a wide range of personal data. --- ### **Stolen Data:** According to a separate filing with the **Massachusetts Attorney General**, DISA revealed that the compromised data includes: - **Social Security Numbers** - **Financial Account Information** (including credit card numbers) - **Government-Issued Identification Documents** Over **360,000** residents of Massachusetts were directly impacted by this breach, though the full scope remains unclear. It is important to note that **DISA has yet to definitively confirm** which data was specifically exfiltrated, suggesting limitations in their **security logging and monitoring systems**. --- ### **Potential Impact:** The breach affects individuals who underwent various **employee screening tests**. These screenings include sensitive data such as: - **Work History** - **Criminal Records** - **Educational Background** - **Credit History** Given the nature of DISA’s services, which cater to over **55,000 enterprises** (including major corporations such as Fortune 500 companies), the breach has widespread implications. The company’s lack of clear technical logs means that the total exposure of data remains uncertain. --- ### **Investigation Status:** DISA’s internal investigation has not identified the perpetrators of the cyberattack. As of the latest update, it remains unclear **how** the breach occurred or the specific **methodology** used by the attacker to infiltrate DISA's systems. Furthermore, there is a significant delay in informing affected individuals, raising concerns about the company’s crisis management protocols and internal security measures. --- ### **Company Response:** DISA has assured the public that they are working to contain the breach and prevent further unauthorized access. They have also initiated procedures to notify all individuals whose data was compromised. However, questions persist about their ability to track and monitor unauthorized data access, given the **lack of logs** and transparency in their internal response. --- ### **Unanswered Questions:** - **Who is responsible for the cyberattack?** - **How was DISA’s system compromised?** - **Why was there such a significant delay in notifying affected individuals?** - **What steps will DISA take to improve their security measures moving forward?** ---

loading..   27-Feb-2025
loading..   3 min read