intelligence_src_5203a44f1436ff5844
- Source-provided label
- Publisher RSS metadata
- Evidence class
- mentioned in report
- Confidence
- Not reported
- Observed
- Sep 28, 2026 04:10 UTC
- Retrieved
- Oct 13, 2026 09:59 UTC
Sicherheitsvorfall - Supabase
Nach Angaben von UpGuard waren rund 16.000 auf Supabase gehostete Datenbanken öffentlich erreichbar. Sie enthielten sensible personenbezogene Daten. Die Erkenntnisse veröffentlichte das Sicherheitsunternehmen am 25. September 2026 in einem Blogbeitrag. Ursache seien Fehlkonfigurationen durch Nutzer gewesen, die Datenbanken ohne ausreichende Zugriffskontrollen betrieben. In einigen Fällen waren Millionen Datensätze exponiert. Der Vorfall zeigt, wie schnell aus einer fehlerhaften Konfiguration ein massives Datenschutzrisiko werden kann, selbst wenn kein klassischer Cyberangriff stattfindet.» Details
Reference details
- Source category
- research-report
- First reported
- Sep 28, 2026 04:10 UTC
- Last reported
- Sep 28, 2026 04:10 UTC
- Catalog updated
- Oct 13, 2026 09:59 UTC
- Record ID
05c9f93dfd612f6f4029d8a3bdcf8747f25edba05610e84306992254e331eca6
Published indicators
Network indicators are visibly defanged. This page does not make them clickable or send them to another service.
No validated file hashes or network indicators are stored for this record.
Source observations
This record contains metadata and attribution only. It does not host, download, unpack, render, or execute malware samples.
Feed collection status
Sources represented on this page. Publication and observation dates describe the content; successful batch dates describe local collection. A recent batch does not certify complete coverage or current provider availability.
1 sources: 0 stale, 0 needing attention, 0 paused, 0 unverified.
Review source update dates and status
- intelligence_src_5203a44f1436ff5844Recent successful batchLast successful batch: Last attempt:
Stale means older than twice the recorded collection interval, with a minimum of one hour; without an interval, the threshold is 24 hours. Cached content remains available while a feed is stale, paused, or unverified.