EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Hacker News·25d ago·5 min read
CrowdSec Source Code Leak
TL;DR
CrowdSec confirmed a source code leak from its private GitHub repositories, primarily affecting its SaaS console and AWS routines. No client data was compromised, and the impact is deemed limited.
✦ Why It Matters
Review your own code repositories for potential vulnerabilities and ensure proper security measures are in place.
Key Takeaways
- Audit your code repositories for security vulnerabilities.
- Rotate credentials regularly to prevent unauthorized access.
- Monitor for abnormal activity following a code leak.
- Ensure no sensitive data is stored in public repositories.
Full Summary
On September 16, CrowdSec acknowledged a source code leak that occurred in May 2026, affecting its private GitHub repositories. The leaked code includes components for their Software as a Service (SaaS) console and AWS Cloud routines, while their public Free Open Source Software remains unaffected.
Although the leak involved around 300 repositories, the majority are public and reflect code subdivision rather than volume. CrowdSec has confirmed that no sensitive client information, such as personal identifiable information (PII) or login credentials, was exposed.
The leak is believed to have originated from a compromised component used in May, which extracted an API key for accessing the private codebase. CrowdSec has since rotated all necessary tokens and credentials to mitigate any potential risks.