# Security / CTI Enrichment Pack — NVD, CIRCL, URLhaus (`cynix_dev/security-cti-pack`) Actor

Enrich a CPE/keyword across threat feeds in one run: NVD CVEs, CIRCL recent CVEs, and URLhaus malware.

- **URL**: https://apify.com/cynix\_dev/security-cti-pack.md
- **Developed by:** [Cynix Dev](https://apify.com/cynix_dev) (community)
- **Categories:** Developer tools, Other, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Security / CTI Enrichment Pack

Correlate vulnerability and threat data across free open-security feeds in one run: **NVD CVEs**, **CIRCL recent CVEs**, and **URLhaus malware URLs**. One flat, typed dataset. Free open threat data — no API key, no proxy.

### What it does

Threat analysts usually juggle three or four dashboards to answer "what's the current CVE exposure for X, and what malicious URLs are trending?" This Actor fuses the key open feeds into one queryable output.

- Search **NVD** by CPE or keyword (`log4j`, `cpe:2.3:a:apache:tomcat`).
- Pull the **most recent CVEs** from CIRCL.
- Pull **recent malicious URLs** from URLhaus.

### Features

- **NVD** — official US NIST CVE database; returns ID, CVSS severity, published date, description.
- **CIRCL CVE API** — most-recent CVEs with CVSS and summaries.
- **URLhaus** — recent malware URLs (CSV feed from abuse.ch), parsed into typed rows.
- **Per-source coverage summary** — every run emits a `RUN_SUMMARY` row listing what was checked and how many hits each source returned.
- **No API key, no proxy** — all sources are free open-security endpoints.

### What people use it for

- **Vulnerability triage** — enumerate CVEs for a product you run.
- **Threat-intel feeds** — pipe recent CVEs / malware URLs into a SIEM or alerting.
- **Daily exposure digest** — schedule a run and watch new CVEs for your stack.
- **Incident response** — confirm whether a flagged CVE or URL is known.

### Understanding the fields

| Field | Meaning |
| --- | --- |
| `source` | NVD / CIRCL / URLhaus / RUN\_SUMMARY |
| `id` | CVE ID or URLhaus ID |
| `severity` | CVSS base severity (NVD/CIRCL) or threat type (URLhaus) |
| `published` | Publication / addition date |
| `detail` | Description or URL |
| `attribution` | Source credit |

### Input

All fields optional; sensible defaults produce a working run.

| Field | Type | Default | What it does |
| --- | --- | --- | --- |
| `cpeQuery` | string | `log4j` | CPE 2.3 string or keyword for NVD search. |
| `recentCount` | integer | `10` | Number of recent CVEs to pull from CIRCL (1–50). |
| `includeNvd` | boolean | `true` | Search NVD for the query. |
| `includeCircl` | boolean | `true` | Pull recent CVEs from CIRCL. |
| `includeUrlhaus` | boolean | `true` | Pull recent malware URLs from URLhaus. |
| `maxResultsPerSource` | integer | `10` | Cap per source (1–50). |

#### Input example

```json
{
  "cpeQuery": "log4j",
  "recentCount": 10,
  "includeNvd": true,
  "includeCircl": true,
  "includeUrlhaus": true,
  "maxResultsPerSource": 10
}
```

### Output

One record per threat hit, plus a `RUN_SUMMARY` row.

```json
{
  "query": "log4j",
  "source": "NVD",
  "id": "CVE-2021-44228",
  "severity": "CRITICAL",
  "published": "2021-12-10T00:00:00.000",
  "detail": "Apache Log4j2 JNDI features...",
  "sourceUrl": "https://nvd.nist.gov/vuln/detail/CVE-2021-44228",
  "attribution": "NVD (NIST, public domain)"
}
```

Export the dataset as JSON, CSV, Excel, XML or JSONL from the Console, or pull it programmatically through the Apify API.

### How to use it

1. Click **Try for free** (or **Start** if you already have an Apify account).
2. Fill in the input fields above — the defaults already produce a working run.
3. Press **Start** and watch the log; results stream into the dataset as they are found.
4. When the run finishes, open the **Output** tab and export as JSON, CSV or Excel.

Runs can be scheduled (hourly, daily, weekly) and wired into Slack, Google Sheets, Zapier, Make, webhooks or your own backend. Everything the Console does is also available over the [Apify API](https://docs.apify.com/api/v2).

### Proxy configuration

Not needed. All sources are free public open-security endpoints that do not block datacenter IPs.

### Pricing

This Actor is billed on Apify's **pay-per-event** model: a small charge when a run starts, plus a charge for each result written to the dataset. You only pay for records you actually receive. Current rates are shown on the **Pricing** tab.

### FAQ

#### Do I need an API key?

No. NVD, CIRCL, and URLhaus are free open services.

#### Is the data authoritative?

Yes — NVD is the US government CVE database; CIRCL and URLhaus are widely used open threat feeds.

#### Why a coverage summary row?

So you can tell "no matches" from "a source failed" — the `RUN_SUMMARY` row reports per-source hit counts explicitly.

### Other Actors by cynix\_dev

| Actor | What it does |
| --- | --- |
| [Pharma / Biotech Intelligence Pack](https://apify.com/cynix_dev/pharma-biotech-pack) | FDA, ClinicalTrials.gov and MedlinePlus genetics in one actor. |
| [ClinicalTrials.gov Extractor](https://apify.com/cynix_dev/clinicaltrials-scraper) | ClinicalTrials.gov v2 API as typed study records. |

### Legal and responsible use

This Actor collects only publicly available information. You are responsible for how you use the data, including compliance with the target site's Terms of Service, robots directives, copyright, and data protection law such as GDPR and CCPA. Do not use it to gather personal data without a lawful basis.

### Support and feedback

Found a bug, hit a site change, or need an extra field? Open a ticket on the **Issues** tab of this Actor — issues are read and fixed. Feature requests and custom-scraper enquiries are welcome through the same channel.

# Actor input Schema

## `cpeQuery` (type: `string`):

CPE 2.3 string or keyword, e.g. 'log4j'.

## `recentCount` (type: `integer`):

Recent CVEs to pull from CIRCL.

## `includeNvd` (type: `boolean`):

Search NVD for the query.

## `includeCircl` (type: `boolean`):

Pull recent CVEs from CIRCL.

## `includeUrlhaus` (type: `boolean`):

Pull recent malware URLs from URLhaus.

## `maxResultsPerSource` (type: `integer`):

Cap per source (1-50).

## Actor input object example

```json
{
  "cpeQuery": "log4j",
  "recentCount": 10,
  "includeNvd": true,
  "includeCircl": true,
  "includeUrlhaus": true,
  "maxResultsPerSource": 10
}
```

# Actor output Schema

## `dataset` (type: `string`):

One record per threat hit: NVD CVE, CIRCL CVE, or URLhaus malware URL.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "cpeQuery": "log4j"
};

// Run the Actor and wait for it to finish
const run = await client.actor("cynix_dev/security-cti-pack").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "cpeQuery": "log4j" }

# Run the Actor and wait for it to finish
run = client.actor("cynix_dev/security-cti-pack").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "cpeQuery": "log4j"
}' |
apify call cynix_dev/security-cti-pack --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,cynix_dev/security-cti-pack"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/UmP6DXDySV5h8CZz6/builds/YlEDNDKHp2CEbB7Zc/openapi.json