3 critical advisoriesLiteLLM 1.107.0·PHP2Shell·GitLab CVE-2026-110264All advisories→

Know about new threats first. Once each, with the full story.

Scout, Vulneron’s intelligence agent, searches everywhere. Every 10 minutes it checks over 30 sources: vendor advisories, government CERTs, threat researchers, package registries and security news. It also scans popular packages itself. Each threat becomes one deduplicated record that updates as the incident develops, and powers every Vulneron product.

TH-2026-1187 · Supply-chain compromise · No CVE yetMalicious release of example-http on npm
Critical · actively exploited
Sources16 merged · 1 record
  • Vulneron Scoutfirst seen · registry scan
  • Independent researcherwrite-up
  • GitHub Advisoriesaffected versions
  • OSVcross-reference
  • Security news · 12context only
History1 alert · 4 follow-ups linked
  1. 09:14Scout flags an obfuscated install script in a new release
  2. 09:42Alert sent: critical, on your watchlist
  3. 10:05Researcher write-up merged into the record
  4. 11:20GitHub advisory adds affected versions
  5. 13:10Maintainer confirms account compromise
  6. 16:45Fixed release published · 12 articles linked
Affected versionsstructured data
  • example-httpaffected 4.2.1, 4.2.2fixed 4.2.3
  • example-http-cliaffected 1.8.0fixed 1.8.1
Exploitability score96
Severity: from the advisory, not the headlinesWatchlist: example-http · alerted 09:42, once
Illustrative product view · sample data
What Scout does

Everything about a threat, in one place. Intelligence you can act on.

When a flaw breaks, the vendor advisory, the CISA notice, the researcher's write-up and a dozen news articles all describe the same thing. Scout combines them into one record and keeps it current.

Powers every product

One set of threat records. Both sides of the loop.

Scout sits in front of all six agents. The side that tests and the side that watches start from the same picture of what is out there, so a new threat changes what gets tested and what gets watched at the same time.

Sources

Over 30 sources, every 10 minutes. Plus our own.

Authoritative sources set severity and remediation. Scout's own registry scanning finds what nobody has reported yet. News adds context.

Vulneron Scout
Package registry scouringScans of popular packages
Vendors
MicrosoftAppleCiscoFortinetPalo Alto NetworksIvantiSonicWallJuniperOracleAtlassianGoogle ChromeMozillaGitLabNode.jsPHP
Government CERTs
CISACERT-EUNCSC-UK
Threat researchers
Zero Day InitiativeCisco TalosUnit 42
Package ecosystems
GitHub AdvisoriesOSV
Security news
Context, never a verdict
FAQ

Threat intelligence questions

How often does Scout check for new threats?
Every 10 minutes, across more than 30 sources, alongside its own scanning of package registries.
Does it cover threats without a CVE?
Yes. Malicious packages, supply-chain compromises, active campaigns and breaches are tracked alongside vulnerabilities, including threats that have no CVE yet.
Where do severity and affected versions come from?
Severity and remediation come from vendors and government agencies first. Affected package versions come from structured advisory data, never from an article and never inferred from NVD’s product listings.
Will we be alerted every time a threat is updated?
No. You hear about what is critical, high, actively exploited, in KEV or on your watchlist, while it is news. Updates are recorded in the threat’s history and follow-up reports link to the original alert.
Is it a separate product?
Scout powers every Vulneron product. The Attack agent, the SOC agents and your alerts all work from the same threat records.

Hear about it first. Hear about it once.

See what Scout is tracking that affects your stack, and how it changes what Vulneron tests and watches.