Vulnerability & Security Intel Aggregator avatar

Vulnerability & Security Intel Aggregator

Pricing

Pay per usage

Go to Apify Store
Vulnerability & Security Intel Aggregator

Vulnerability & Security Intel Aggregator

Pull live security intel from GitHub Advisories, MITRE ATT&CK, Exploit DB, OpenSSF Scorecard and URLhaus in one feed. Get CVE IDs, severity, affected packages, threat techniques and active malware URLs. Built for SecOps, threat intel and DevSecOps.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

ParseForge

ParseForge

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

ParseForge Banner

๐Ÿ›ก๏ธ Vulnerability & Security Intel Aggregator

๐Ÿš€ Query 5 authoritative security feeds in one run. GitHub GHSA advisories, MITRE ATT&CK techniques, Exploit-DB exploits, OpenSSF Scorecard projects and URLhaus malware URLs - aggregated, normalized, exported.

๐Ÿ•’ Last updated: 2026-05-27 ยท ๐Ÿ“Š 10 fields per record ยท 5 sources ยท global vulnerability, exploit, malware and supply-chain intelligence

The Vulnerability & Security Intel Aggregator queries five independent security data sources in parallel and returns a unified stream of records. Each record is tagged with its source so you can filter, dedupe or split by platform downstream.

The combination spans coordinated disclosures (GHSA), adversary tradecraft (MITRE ATT&CK), proof-of-concept exploits (Exploit-DB), open-source supply-chain hygiene (OpenSSF Scorecard) and active malware infrastructure (URLhaus).

๐ŸŽฏ Target Audience๐Ÿ’ก Primary Use Cases
SOC / DFIR / threat intel teamsDaily intel feed
AppSec / DevSecOpsDependency risk scoring
Red teams / pentestersExploit and TTP lookup
CTI vendors and researchersCross-source enrichment

๐Ÿ“‹ What the Vulnerability & Security Intel Aggregator does

  • Queries up to 5 distinct security APIs and feeds in parallel (Promise.allSettled)
  • Applies a unified keyword across every source that exposes search
  • Normalizes every record to the same 10-field shape
  • Returns one tagged stream - source: ghsa | mitre | exploitdb | openssf | urlhaus
  • Continues with the remaining sources if one fails

๐Ÿ’ก Why it matters: one input, one dataset, five authoritative security feeds.

๐ŸŽฌ Full Demo (๐Ÿšง Coming soon)

โš™๏ธ Input

FieldTypeRequiredDescription
querystringnoKeyword applied to GHSA, MITRE, Exploit-DB
sourcesarray of enumnoSubset of ghsa, mitre, exploitdb, openssf, urlhaus
maxItemsintegernoFree 10 / Paid up to 1,000,000
openssfReposarraynoRepos to score against OpenSSF Scorecard
proxyConfigurationobjectnoApify Proxy (recommended for Exploit-DB)
{
"maxItems": 20,
"sources": ["ghsa", "mitre", "exploitdb", "openssf", "urlhaus"]
}
{
"query": "rce",
"maxItems": 30,
"sources": ["ghsa", "exploitdb"]
}

โš ๏ธ Good to Know: OpenSSF Scorecard needs an explicit list of repos. URLhaus and MITRE are public bulk feeds - the keyword is matched client-side.

๐Ÿ“Š Output

FieldTypeDescription
๐Ÿ“ก sourcestringghsa / mitre / exploitdb / openssf / urlhaus
๐Ÿ“Œ titlestringAdvisory summary, technique name, exploit title, repo name, malware host
๐Ÿ”— urlstringCanonical URL on the source site
๐Ÿ†” idstringGHSA ID / Txxxx / EDB ID / repo / URLhaus ID
โš ๏ธ severitystringcritical/high/etc. (GHSA), verified flag (Exploit-DB), URL status (URLhaus)
๐Ÿท๏ธ categorystringCWE / technique vs. sub-technique / exploit type / threat type
๐Ÿ•’ datestringPublished / disclosed date
๐Ÿ“ summarystringSource-specific summary
+ source-specific fieldsvariescveId, platform, score, checks, host, tags, etc.
๐Ÿ•’ scrapedAtstringISO timestamp
โŒ errorstringPer-source error record (rare)

โœจ Why choose this Actor

DifferentiatorDetail
๐ŸŒ Five sources, one runSave engineering and credits
๐Ÿ›ก๏ธ ResilientOne source failure does not stop the others
โšก Parallel fetchConcurrent fetchers
๐Ÿงฉ Unified schemaSame shape for every source
๐Ÿ“ฆ Pay-per-eventPay only for records collected

๐Ÿ“ˆ How it compares to alternatives

AlternativeThis Aggregator
Buy a CTI feedNo subscription, public sources only
Run 5 separate scrapersSingle run, single dataset
Build CVE-correlator yourselfSchema already normalized

๐Ÿš€ How to use

  1. Create a free account w/ $5 credit
  2. Open the actor on Apify console
  3. Pick sources (default = all 5)
  4. Set query, openssfRepos, maxItems
  5. Run

๐Ÿ’ผ Business use cases

SOC and DFIR

NeedHow
Daily threat intel feedSchedule daily, ingest into SIEM
IOC enrichmentCross URLhaus with internal proxy logs

AppSec / DevSecOps

NeedHow
SCA pre-screenGHSA + OpenSSF for every release
Dependency hygieneOpenSSF scores on every direct dependency

Red team / pentest

NeedHow
TTP lookupMITRE ATT&CK by keyword
Exploit researchExploit-DB filtered by CVE / platform

CTI / research

NeedHow
Cross-source enrichmentJoin GHSA + MITRE + Exploit-DB on CVE
Supply-chain risk modelOpenSSF Scorecard portfolio scoring

๐Ÿ”Œ Automating Vulnerability & Security Intel

  • Make / Zapier - push every new record to Slack, Jira, ServiceNow
  • Slack - daily critical-CVE digest
  • Airbyte / Fivetran - sync to your warehouse
  • GitHub Actions - fail builds on new high-severity advisory
  • Webhooks - push to your SOAR/SIEM

๐ŸŒŸ Beyond business use cases

Research

  • Cross-source CVE coverage analysis
  • Adversary TTP evolution studies

Personal

  • Track CVEs in your stack
  • Monitor your favourite OSS projects

Non-profit

  • Public-sector vulnerability tracking
  • Election-infrastructure monitoring

Experimentation

  • LLM-powered advisory triage
  • Knowledge graphs across vuln, exploit and TTP

๐Ÿค– Ask an AI assistant about this scraper

โ“ Frequently Asked Questions

โ“ Which sources? GHSA (GitHub Advisories), MITRE ATT&CK (Enterprise techniques), Exploit-DB, OpenSSF Scorecard, URLhaus.

โ“ Can I pick a subset? Yes via the sources array.

โ“ Do I need API keys? No. All sources expose public, unauthenticated endpoints.

โ“ What if one source fails? Others keep going. The failing source emits an error record.

โ“ How do I look up an exploit for a CVE? Pass the CVE as query and limit sources to ["ghsa","exploitdb"].

โ“ Why OpenSSF Scorecard? Adds supply-chain hygiene scoring on top of pure vulnerability data.

โ“ Is URLhaus output verified? Yes - abuse.ch maintains an active malware URL list.

โ“ How fresh is the data? Real-time. Each source is queried live per run.

โ“ Pricing model? Pay-per-event: billed per record actually pushed.

โ“ Can I schedule it? Yes - use Apify Schedules.

๐Ÿ”Œ Integrate with any app

  • Make, Zapier, n8n, Pipedream
  • Airbyte, Fivetran, Stitch
  • Slack, Discord, Microsoft Teams
  • Jira, ServiceNow, PagerDuty
  • Splunk, Elastic, Datadog
  • GitHub Actions, GitLab CI
  • Webhooks, REST API, S3, GCS
ActorWhy
MITRE ATT&CK Techniques ScraperStandalone ATT&CK
Exploit-DB Exploits ScraperStandalone Exploit-DB
OpenSSF Scorecard Projects ScraperStandalone OpenSSF
URLhaus Malware URLs ScraperStandalone URLhaus

๐Ÿ’ก Pro Tip: browse the complete ParseForge collection.

๐Ÿ†˜ Need Help? Open our contact form

โš ๏ธ Disclaimer: independent tool, not affiliated with GitHub, MITRE, Offensive Security, OpenSSF or abuse.ch. Only publicly available data is collected.