Team4Security Alleged Data Breach: Ransom Demand and Potential Risks Unveiled

Team4Security Alleged Data Breach: Ransom Demand and Potential Risks Unveiled

Tuesday, March 10, 2026

Top 5 Cybersecurity Stories You Should Know

  1. Team4Security Alleged Data Breach: Ransom Demand and Potential Risks Unveiled — tl;dr: On March 7, 2026, a user named ‘GhostCrawl’ claimed a data breach at Team4Security on Breachforums.as, demanding a ransom of $2,350 and threatening to disclose sensitive information within 24 hours. While the claims remain unverified, they highlight significant risks including potential exposure of internal documents and client credentials. Organizations are advised to monitor for unusual access patterns, conduct internal reviews, and activate incident response teams. This incident underscores the importance of proactive cybersecurity measures and the need for vigilance against evolving threats in the digital landscape.
    ↪ https://darknetsearch.com/knowledge/news/en/team4security-data-breach-7-urgent-facts-revealed/
  2. LexisNexis Data Breach Exposes Salesforce Credentials of 400,000 Users — tl;dr: A significant data breach at LexisNexis has compromised over 3.9 million records, affecting approximately 400,000 users, including U.S. government officials. The hacking group FulcrumSec exploited a vulnerable React application, exposing unencrypted credentials and sensitive customer data. LexisNexis confirmed the breach but stated that the compromised data was mostly outdated and did not include sensitive personal information like Social Security numbers. Salesforce has indicated no vulnerability in its platform. Organizations using LexisNexis should review their security measures and monitor for unusual activity to mitigate potential risks.
    ↪ https://www.salesforceben.com/lexisnexis-data-breach-salesforce-credentials-exposed-in-3-9m-record-hack/
  3. Ericsson US Reports Data Breach from Third-Party Provider Affecting Employees and Customers — tl;dr: Ericsson’s U.S. subsidiary has reported a data breach linked to an unnamed third-party service provider, affecting both employees and customers. The breach, which occurred between April 17 and April 22, 2025, involved unauthorized access to sensitive personal data, including Social Security numbers and financial information. Although the FBI was notified and an investigation found no evidence of misuse, impacted individuals in California and Texas have been offered complimentary identity protection services. Those affected are encouraged to enroll in these services by June 9, 2026, to safeguard against potential identity theft.
    ↪ https://www.crn.com/news/security/2026/ericsson-u-s-unit-reports-data-breach-tied-to-third-party-service-provider
  4. CVE Program Secures Funding, Ensuring Stability for Vulnerability Tracking — tl;dr: The funding crisis threatening the Common Vulnerabilities and Exposures (CVE) program has been resolved, with the Cybersecurity and Infrastructure Security Agency (CISA) and MITRE Corporation renegotiating their contract. This change elevates the CVE program from discretionary funding to a protected budget line, ensuring its continued operation and modernization. While the cybersecurity community can breathe easier, concerns remain about transparency and governance. Stakeholders are encouraged to seek clarity on performance metrics and governance as the program evolves, especially given the backdrop of emerging alternative vulnerability frameworks.
    ↪ https://www.csoonline.com/article/4142600/cve-program-funding-secured-easing-fears-of-repeat-crisis.html
  5. LexisNexis Breach Exposes Sensitive Data via React2Shell Vulnerability (CVE-2025-55182) — tl;dr: The recent breach of LexisNexis’ cloud infrastructure by the threat group FulcrumSec exploited the React2Shell vulnerability (CVE-2025-55182) in an unpatched AWS application, compromising sensitive data including government PII, internal security reports, and customer credentials. This incident poses significant risks for over 7,500 government agencies and 85% of Fortune 500 companies that rely on LexisNexis services. Organizations are advised to immediately rotate secrets, enforce password resets, and enhance identity verification to mitigate potential threats stemming from this breach.
    ↪ https://www.dataminr.com/resources/intel-brief/lexis-nexis-breach-cloudinfrastructure/

AI Risk Inspector (Tool) — Scan AI models for risks and export client-ready reports.
Explore →


Connect with LufSec