Was AbuseIPDB.APIv2 Hacked?

No Publicly Reported Incidents. As of June 2026, AbuseIPDB.APIv2 has no publicly reported security breaches, hacks, or CVE entries in the databases Nerq monitors. This covers the National Vulnerability Database (NVD), GitHub Security Advisories, and OSV.dev. Nerq's automated security analysis rates AbuseIPDB.APIv2's security posture as strong (security dimension score: 90/100). Trust Score: 64/100 (C+). Last checked: 2026-06-15.

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score64/100 (C+)
Security Dimension90/100
PublisherMichael Hidalgo
RegistryN/A

What We Check

Full Trust Analysis

For a complete safety assessment including privacy, maintenance, and community trust signals, see AbuseIPDB.APIv2 Trust Score on Nerq.

FAQ

Has AbuseIPDB.APIv2 been hacked?
As of June 2026, AbuseIPDB.APIv2 has no publicly reported security breaches, hacks, or CVE entries in the databases Nerq monitors. This covers the National Vulnerability Database (NVD), GitHub Security Advisories, and OSV.dev.
How many CVEs does AbuseIPDB.APIv2 have?
AbuseIPDB.APIv2 has 0 CVE entries (0 critical). CVEs are publicly disclosed vulnerabilities tracked by MITRE and the NVD.
Is AbuseIPDB.APIv2 safe to use after a breach?
With no reported breaches, AbuseIPDB.APIv2 appears safe based on available data.
Where can I check AbuseIPDB.APIv2's security history?
Nerq monitors NVD (nvd.nist.gov), GitHub Security Advisories, and OSV.dev for AbuseIPDB.APIv2. View the full trust analysis at nerq.ai/safe/abuseipdb-apiv2.

Updated June 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy