Was 00225 Hacked?

No Publicly Reported Incidents. As of April 2026, 00225 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. Trust Score: 38/100 (E). Last checked: 2026-04-26.

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score38/100 (E)
Publisher0x9d225a78be9bda7d747d66852e9c582a10f87f86
RegistryN/A

What We Check

Full Trust Analysis

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

FAQ

Has 00225 been hacked?
As of April 2026, 00225 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 00225 have?
00225 has 0 CVE entries (0 critical). CVEs are publicly disclosed vulnerabilities tracked by MITRE and the NVD.
Is 00225 safe to use after a breach?
With no reported breaches, 00225 appears safe based on available data.
Where can I check 00225's security history?
Nerq monitors NVD (nvd.nist.gov), GitHub Security Advisories, and OSV.dev for 00225. View the full trust analysis at nerq.ai/safe/00225.

Updated April 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy