DebugBear says DNS records were hijacked via its domain registrar
DebugBear says attackers compromised its DNS records through its domain registrar.
Written by a model from the sources below. Verify against them.
- Vendor
- DebugBear
- Status
- Reported, not confirmed
- Disclosed
Summary
Early findings show a single customer was targeted, and Polymarket returned $3.9 million to traders.
What to do
Check DNS records for unexpected changes
Review registrar account access and enable registrar lock
Enable multi-factor authentication on the registrar account
Verify DebugBear's official statements before acting on related notices
Timeline
- Made public by SecurityWeek
- First seen by cve.now
Evidence 1
- PressSecurityWeek
“DebugBear says its DNS records were compromised via its domain registrar, and early findings show a single customer was targeted.”
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about the DebugBear breach
Was DebugBear breached?
SecurityWeek reports it. No statement from DebugBear has reached cve.now yet.
What should DebugBear customers do?
Check DNS records for unexpected changes. Review registrar account access and enable registrar lock. Enable multi-factor authentication on the registrar account. Verify DebugBear's official statements before acting on related notices.