Was 22552 Hacked?
No Publicly Reported Incidents. As of April 2026, 22552 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-25.
No Publicly Reported Incidents
Security Incident Summary
| CVE Count | 0 |
|---|---|
| Critical CVEs | 0 |
| Breach Status | No Publicly Reported Incidents |
| Trust Score | 38/100 (E) |
| Publisher | 0x2992a6bc5d1f67d4b00501968df1b332d71a16e7 |
| Registry | N/A |
What We Check
- National Vulnerability Database (NVD) — CVE entries for publicly disclosed vulnerabilities
- GitHub Security Advisories — security alerts for open-source dependencies
- OSV.dev — Google's open-source vulnerability database
- Public breach reports — media reports and incident disclosures
Full Trust Analysis
For a complete safety assessment including privacy, maintenance, and community trust signals, see 22552 Trust Score on Nerq.
FAQ
Has 22552 been hacked?
As of April 2026, 22552 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 22552 have?
22552 has 0 CVE entries (0 critical). CVEs are publicly disclosed vulnerabilities tracked by MITRE and the NVD.
Is 22552 safe to use after a breach?
With no reported breaches, 22552 appears safe based on available data.
Where can I check 22552's security history?
Nerq monitors NVD (nvd.nist.gov), GitHub Security Advisories, and OSV.dev for 22552. View the full trust analysis at nerq.ai/safe/22552.
Safe? Legit? Scam?
Spyware? Privacy Pros/Cons
Review What is it? Who owns?
Alternatives Use safely
Kids? Trending Leaderboard
Updated April 2026. Trust scores based on automated analysis.