Zero Radar

How Zero Radar works

Zero Radar collects new security flaws, attacks and leaks from 40 sources, merges reports about the same issue into one entry and explains it in plain words. It runs continuously: each source is checked on its own schedule, and the site updates within seconds of new information.

From first report to entry

  1. Watch. Every source is polled on its own interval, the fastest every minute. Unchanged feeds cost almost nothing, so we can ask often.
  2. Merge. Reports that name the same CVE are joined. Reports without a CVE are compared by an AI model and merged when they describe the same incident. Two different CVEs are never merged.
  3. Explain. For important entries an AI model writes the plain-language text, the attack diagram and the steps, using only the collected sources. Versions, dates and exploitation come from the sources themselves.
  4. Keep watching. Entries stay open for 30 days. When a source reports attacks or a patched version later, the entry changes right away and the timeline shows when.

How sure is an entry?

No report is thrown away, but each one is labelled by how well it is backed:

Official sourceAt least one vendor, CERT or advisory database reports it.
Several sourcesTwo or more independent publishers report it. Overlap makes false alarms unlikely.
Single reportOne researcher or newsroom so far. Probably real, but details may change.
UnverifiedOnly community posts. Shown so you hear early, ranked lower until someone confirms it.

“Exploited in the wild” needs an official source such as CISA KEV or the vendor. If only researchers or the press report attacks, the entry says “attacks reported”.

Trust levels

OfficialVendors, government CERTs and advisory databases. Their word on exploitation and fixes counts as confirmed.
ResearchersSecurity research teams and disclosure mailing lists. Often first, usually right.
PressEstablished security newsrooms. Good for context, counted as a report, not as confirmation.
CommunityDiscussion sites. Used as an early hint only; never enough on its own to say “exploited”.

Databases

SourceWhat it addsChecked every
GitHub Advisory Databasereviewed advisories with affected and fixed package versions1 min
NVD (NIST)every new CVE, CVSS scores, patch links5 min
CISA KEVofficial list of flaws known to be exploited5 min
OSVfixed versions that appear after the first report15 min
FIRST EPSSprobability of exploitation in the next 30 days6 h
Have I Been Pwnedverified data breaches30 min
Hacker Newsearly signals, only with 25+ points3 min

Feeds

SourceTrustChecked every
PHPOfficial2 min
GitLabOfficial2 min
Node.jsOfficial2 min
oss-securityResearchers2 min
BleepingComputerPress2 min
The Hacker NewsPress2 min
SecurityWeekPress3 min
Google ChromeOfficial5 min
Microsoft MSRCOfficial5 min
WordPressOfficial5 min
KubernetesOfficial5 min
DjangoOfficial5 min
PythonOfficial5 min
GitHub Security BlogOfficial5 min
Cisco PSIRTOfficial5 min
Fortinet PSIRTOfficial5 min
Palo Alto NetworksOfficial5 min
Debian SecurityOfficial5 min
Ubuntu SecurityOfficial5 min
CISAOfficial5 min
CERT-Bund (BSI)Official5 min
Full DisclosureResearchers5 min
SocketResearchers5 min
The RecordPress5 min
Dark ReadingPress5 min
DataBreaches.netPress5 min
r/netsecCommunity5 min
RustOfficial10 min
JenkinsOfficial10 min
CERT-EUOfficial10 min
NCSC UKOfficial10 min
watchTowr LabsResearchers10 min
Wiz ResearchResearchers10 min

What Zero Radar does not do

Code and pipeline are open source on GitHub. To get entries in your tools, see Integrate.