India CyberThreat Pulse API

Programmatic access to India-focused threat intelligence: incidents and ransomware leak-site victims, CERT-In advisories, indicators of compromise and actively exploited vulnerabilities (CISA KEV + EPSS). Data refreshes every 2 hours.

Base URL

https://pulse.krishnamuduli.co.in

Auth

Bearer API key

Format

JSON · RFC 9457 errors

Version

v1 · 1.1.0

Quick start

  1. Get an API key (B2B or Enterprise plan). For the demo, create one in Supabase SQL: select create_api_key('Demo – Postman', 'b2b');
  2. Call GET /api/v1/me with Authorization: Bearer <key> to check it.
  3. Download the Postman collection or import the OpenAPI spec into any client.
cURL
curl -s https://pulse.krishnamuduli.co.in/api/v1/me \
  -H "Authorization: Bearer $PULSE_API_KEY" | jq .

Authentication & API keys

  • Send the key in the header: Authorization: Bearer ctp_live_…. Never in the URL (URLs end up in logs and browser history).
  • Format: ctp_live_ + 48 hex characters. The prefix lets secret scanners (e.g. GitHub) recognise leaked keys.
  • Only a SHA-256 hash is stored; the key is shown once when created. A database leak does not reveal keys.
  • Keys have scopes, an expiry (default 365 days), a per-minute rate limit and a monthly quota, and can be revoked instantly.
  • Use keys from servers only. Never ship them in browser or mobile code.
ScopeGrants
read:incidents/api/v1/incidents
read:advisories/api/v1/cert-alerts
read:iocs/api/v1/iocs
read:kev/api/v1/kev
read:ransomware/api/v1/ransomware-victims
(any valid key)/api/v1/me
Key management (Supabase SQL editor, not exposed over HTTP)SQL
-- Full-access demo key (30 req/min, 5000/month, expires in 365 days)
select create_api_key('Demo – Postman', 'b2b');

-- Scope demo: only IOCs (calls to /kev return 403)
select create_api_key('IOC-only demo', 'b2b', array['read:iocs']);

-- Rate-limit demo: 5 requests per minute
select create_api_key('Rate-limit demo', 'b2b', null, 5);

-- Revoke by prefix (shown in /me and the audit log)
select revoke_api_key('ctp_live_3f9a1c7');

-- Audit trail: who called what
select created_at, key_prefix, method, path, status from api_request_log order by created_at desc limit 20;

Endpoints

MethodPathScopeDescription
GET/api/v1/incidentsread:incidentsCyber incidents
GET/api/v1/cert-alertsread:advisoriesCERT-In advisories
GET/api/v1/iocsread:iocsIndicators of compromise
GET/api/v1/kevread:kevExploited vulnerabilities (CISA KEV)
GET/api/v1/ransomware-victimsread:ransomwareRansomware leak-site victims
GET/api/v1/meany keyCurrent API key
GET/api/v1/healthpublicLiveness check
GET/api/v1/openapi.jsonpublicOpenAPI 3.1 spec
GET/api/v1/postmanpublicPostman collection (download)

List responses are paginated with limit / offset; meta.next_offset is null on the last page. Unknown or repeated parameters return 400.

GET/api/v1/incidentsread:incidents

Cyber incidents

Incidents affecting India and global headlines: ransomware leak-site victims and security news, newest first.

Query parameters

NameRuleDescription
limitinteger 1–200 (default 50)Results per page (1–200).
offsetinteger 0–10000 (default 0)Number of results to skip (0–10000).
severityone of: Critical, High, Medium, LowFilter by severity.
attack_typeone of: Ransomware, Data Breach, DDoS, Phishing, Fraud & Scams, Vulnerability, Malware, Policy & Advisory, Cyber IncidentFilter by attack type.
sectorone of: Finance, Healthcare, Govt/PSU, Telecom, Energy, Education, Transport, Retail, Manufacturing, IT/SaaSFilter by targeted sector.
countrytext ≤6: ISO 3166-1 alpha-2 code (e.g. IN) or GlobalVictim country (IN = India).
actortext ≤60: Letters, digits, spaces and . , ' & ( ) / + _ - onlyThreat actor / ransomware group (partial match).
fromdate YYYY-MM-DDEarliest date, inclusive (YYYY-MM-DD, UTC).
todate YYYY-MM-DDLatest date, inclusive (YYYY-MM-DD, UTC).

Response fields (data[])

FieldTypeDescription
idstringUnique incident ID (UUID).
titlestringHeadline or "Ransomware Attack: <victim>".
descriptionstring | nullSummary (max ~500 chars).
actorstring | nullThreat actor or ransomware group.
countrystringISO country code of the victim, or Global.
statestring | nullIndian state, when stated in the report.
sectorstring | nullTargeted sector.
attack_typestringAttack classification.
severitystringCritical, High, Medium or Low.
sourcestringFeed or publisher the record came from.
urlstring | nullLink to the original public article (never leak-site links).
created_atstring (date-time)When the incident was published or discovered (UTC).
Request
curl -s "https://pulse.krishnamuduli.co.in/api/v1/incidents?country=IN&severity=Critical&limit=10" \
  -H "Authorization: Bearer $PULSE_API_KEY" | jq .
200 responseJSON
{
  "data": [
    {
      "id": "6f1d…",
      "title": "Ransomware Attack: Example Diagnostics Pvt Ltd",
      "description": "Listed on the qilin leak site",
      "actor": "qilin",
      "country": "IN",
      "state": "Maharashtra",
      "sector": "Healthcare",
      "attack_type": "Ransomware",
      "severity": "Critical",
      "source": "Ransomware.live",
      "url": "https://example-diagnostics.in",
      "created_at": "2026-09-30T11:42:00Z"
    }
  ],
  "meta": {
    "request_id": "3b0f6c1e-8a2d-4f7e-9d61-2c5a7e0b9f14",
    "api_version": "1.1.0",
    "generated_at": "2026-10-02T09:15:04.120Z",
    "count": 1,
    "total": 128,
    "limit": 10,
    "offset": 0,
    "next_offset": 10
  }
}
GET/api/v1/cert-alertsread:advisories

CERT-In advisories

CERT-In vulnerability notes and advisories (direct feed, or news coverage when the feed is unavailable).

Query parameters

NameRuleDescription
limitinteger 1–100 (default 50)Results per page (1–100).
offsetinteger 0–10000 (default 0)Number of results to skip (0–10000).
severityone of: Critical, High, Medium, LowFilter by severity.
fromdate YYYY-MM-DDEarliest date, inclusive (YYYY-MM-DD, UTC).
todate YYYY-MM-DDLatest date, inclusive (YYYY-MM-DD, UTC).

Response fields (data[])

FieldTypeDescription
idstringUnique ID (UUID).
alert_idstringCERT-In ID (CIVN-/CIAD-…) or NEWS-<hash> for news coverage.
titlestringAdvisory title.
severitystringCritical, High or Medium.
sourcestring | nullCERT-In, or "CERT-In via <publisher>".
urlstring | nullLink to the advisory or article.
published_atstring (date-time)Publication time (UTC).
Request
curl -s "https://pulse.krishnamuduli.co.in/api/v1/cert-alerts?limit=5" \
  -H "Authorization: Bearer $PULSE_API_KEY" | jq .
200 responseJSON
{
  "data": [
    {
      "id": "a91c…",
      "alert_id": "CIVN-2026-0412",
      "title": "Multiple vulnerabilities in Apple products",
      "severity": "High",
      "source": "CERT-In",
      "url": "https://www.cert-in.org.in/…",
      "published_at": "2026-09-29T06:30:00Z"
    }
  ],
  "meta": {
    "request_id": "3b0f6c1e-8a2d-4f7e-9d61-2c5a7e0b9f14",
    "api_version": "1.1.0",
    "generated_at": "2026-10-02T09:15:04.120Z",
    "count": 1,
    "total": 128,
    "limit": 10,
    "offset": 0,
    "next_offset": 10
  }
}
GET/api/v1/iocsread:iocs

Indicators of compromise

Fresh IOCs from abuse.ch ThreatFox and malware URLs on Indian (.in) domains from URLhaus.

Query parameters

NameRuleDescription
limitinteger 1–500 (default 50)Results per page (1–500).
offsetinteger 0–10000 (default 0)Number of results to skip (0–10000).
ioc_typeone of: url, domain, ip:port, sha256_hash, md5_hash, sha1_hashFilter by indicator type.
malware_familytext ≤60: Letters, digits, spaces and . , ' & ( ) / + _ - onlyMalware family (partial match), e.g. Vidar.
min_confidenceinteger 0–100Minimum confidence (0–100).
sourceone of: ThreatFox, URLhaus .inFilter by feed.
fromdate YYYY-MM-DDEarliest date, inclusive (YYYY-MM-DD, UTC).

Response fields (data[])

FieldTypeDescription
idstringUnique ID (UUID).
ioc_valuestringThe indicator (URL, domain, IP:port or hash). Treat as malicious, do not open.
ioc_typestringIndicator type.
threat_typestring | nulle.g. botnet_cc, payload_delivery, malware_download.
malware_familystring | nullMalware family, when known.
confidenceintegerConfidence 0–100.
countrystring | nullHosting country (URLhaus only).
sourcestringThreatFox or URLhaus .in.
first_seenstring (date-time)First seen (UTC).
Request
curl -s "https://pulse.krishnamuduli.co.in/api/v1/iocs?min_confidence=90&limit=20" \
  -H "Authorization: Bearer $PULSE_API_KEY" | jq .
200 responseJSON
{
  "data": [
    {
      "id": "c2e7…",
      "ioc_value": "185.33.86.141:443",
      "ioc_type": "ip:port",
      "threat_type": "botnet_cc",
      "malware_family": "Vidar",
      "confidence": 100,
      "country": null,
      "source": "ThreatFox",
      "first_seen": "2026-10-02T04:05:08Z"
    }
  ],
  "meta": {
    "request_id": "3b0f6c1e-8a2d-4f7e-9d61-2c5a7e0b9f14",
    "api_version": "1.1.0",
    "generated_at": "2026-10-02T09:15:04.120Z",
    "count": 1,
    "total": 128,
    "limit": 10,
    "offset": 0,
    "next_offset": 10
  }
}
GET/api/v1/kevread:kev

Exploited vulnerabilities (CISA KEV)

Vulnerabilities CISA has confirmed as exploited in the wild, enriched with FIRST EPSS exploitation probability.

Query parameters

NameRuleDescription
limitinteger 1–200 (default 50)Results per page (1–200).
offsetinteger 0–10000 (default 0)Number of results to skip (0–10000).
vendortext ≤60: Letters, digits, spaces and . , ' & ( ) / + _ - onlyVendor (partial match), e.g. Cisco.
ransomware_usetrue | falseOnly CVEs known to be used in ransomware campaigns.
min_epssnumber 0–1Minimum EPSS probability (0–1).
fromdate YYYY-MM-DDEarliest date, inclusive (YYYY-MM-DD, UTC).
todate YYYY-MM-DDLatest date, inclusive (YYYY-MM-DD, UTC).

Response fields (data[])

FieldTypeDescription
cvestringCVE identifier.
vendorstringVendor / project.
productstringProduct.
namestringVulnerability name.
descriptionstringShort description from CISA.
required_actionstringCISA required action.
date_addedstring (date)Date added to KEV.
due_datestring (date)Remediation due date for US federal agencies.
ransomware_usebooleanKnown use in ransomware campaigns.
epssnumberProbability of exploitation in the next 30 days (0–1), or null.
percentilenumberEPSS percentile (0–1), or null.
Request
curl -s "https://pulse.krishnamuduli.co.in/api/v1/kev?min_epss=0.5&limit=10" \
  -H "Authorization: Bearer $PULSE_API_KEY" | jq .
200 responseJSON
{
  "data": [
    {
      "cve": "CVE-2026-20079",
      "vendor": "Cisco",
      "product": "Secure Firewall Management Center",
      "name": "Cisco FMC Authentication Bypass",
      "description": "…",
      "required_action": "Apply mitigations per vendor instructions…",
      "date_added": "2026-09-09",
      "due_date": "2026-09-30",
      "ransomware_use": false,
      "epss": 0.88,
      "percentile": 0.99
    }
  ],
  "meta": {
    "request_id": "3b0f6c1e-8a2d-4f7e-9d61-2c5a7e0b9f14",
    "api_version": "1.1.0",
    "generated_at": "2026-10-02T09:15:04.120Z",
    "count": 1,
    "total": 128,
    "limit": 10,
    "offset": 0,
    "next_offset": 10
  }
}
GET/api/v1/ransomware-victimsread:ransomware

Ransomware leak-site victims

Organisations claimed on ransomware leak sites (via ransomware.live). Claims are made by attackers and not confirmed by victims.

Query parameters

NameRuleDescription
limitinteger 1–200 (default 50)Results per page (1–200).
offsetinteger 0–10000 (default 0)Number of results to skip (0–10000).
countrytext ≤2: ISO 3166-1 alpha-2 code, e.g. INVictim country.
grouptext ≤60: Letters, digits, spaces and . , ' & ( ) / + _ - onlyRansomware group (partial match), e.g. qilin.
fromdate YYYY-MM-DDEarliest date, inclusive (YYYY-MM-DD, UTC).
todate YYYY-MM-DDLatest date, inclusive (YYYY-MM-DD, UTC).

Response fields (data[])

FieldTypeDescription
idstringUnique ID (UUID).
victimstringClaimed victim organisation.
groupstringRansomware group.
countrystringVictim country (ISO code).
sectorstring | nullSector, when known.
discovered_atstring (date-time)When the claim was posted/discovered (UTC).
group_urlstringPublic ransomware.live page for the group (leak-site .onion links are never returned).
Request
curl -s "https://pulse.krishnamuduli.co.in/api/v1/ransomware-victims?country=IN&limit=10" \
  -H "Authorization: Bearer $PULSE_API_KEY" | jq .
200 responseJSON
{
  "data": [
    {
      "id": "9b4a…",
      "victim": "Example Logistics India",
      "group": "akira",
      "country": "IN",
      "sector": "Transport",
      "discovered_at": "2026-09-21T08:10:00Z",
      "group_url": "https://www.ransomware.live/group/akira"
    }
  ],
  "meta": {
    "request_id": "3b0f6c1e-8a2d-4f7e-9d61-2c5a7e0b9f14",
    "api_version": "1.1.0",
    "generated_at": "2026-10-02T09:15:04.120Z",
    "count": 1,
    "total": 128,
    "limit": 10,
    "offset": 0,
    "next_offset": 10
  }
}
GET/api/v1/meany valid key

Current API key

Details of the key making the request: plan, scopes, limits and current usage. Useful to test a key.

Query parameters

None. Any parameter returns 400.

Response fields (data)

FieldTypeDescription
key_prefixstringFirst 16 characters of the key (safe to display).
namestringKey label.
planstringb2b or enterprise.
scopesstring[]Granted scopes.
rate_limit_per_minintegerRequests allowed per minute.
monthly_quotaintegerRequests allowed per calendar month.
used_this_monthintegerRequests counted this month (including this one).
expires_atstring | nullExpiry time, if set.
Request
curl -s "https://pulse.krishnamuduli.co.in/api/v1/me" \
  -H "Authorization: Bearer $PULSE_API_KEY" | jq .
200 responseJSON
{
  "data": {
    "key_prefix": "ctp_live_3f9a1c7",
    "name": "Demo – Postman",
    "plan": "b2b",
    "scopes": [
      "read:incidents",
      "read:advisories",
      "read:iocs",
      "read:kev",
      "read:ransomware"
    ],
    "rate_limit_per_min": 30,
    "monthly_quota": 5000,
    "used_this_month": 42,
    "expires_at": "2027-10-02T09:00:00Z"
  },
  "meta": {
    "request_id": "3b0f6c1e-8a2d-4f7e-9d61-2c5a7e0b9f14",
    "api_version": "1.1.0",
    "generated_at": "2026-10-02T09:15:04.120Z"
  }
}

Rate limits, quotas & response headers

PlanPer minutePer month
B2B305,000
Enterprise120100,000
Any client, failed auth20–

Limits are fixed windows counted atomically in the database, so they hold across all serverless instances. When the limiter is unavailable, requests fail closed (503).

HeaderMeaning
X-Request-IdUnique ID for this request. Quote it to support; it is also in the audit log.
RateLimit-LimitRequests allowed per minute for this key (IETF RateLimit draft).
RateLimit-RemainingRequests left in the current minute.
RateLimit-ResetSeconds until the minute window resets.
X-RateLimit-Limit / -Remaining / -ResetSame values in the widely used X- form (Reset is a Unix timestamp).
X-Quota-Limit / X-Quota-RemainingMonthly quota and requests left this month.
Retry-AfterOn 429: seconds to wait before retrying.
Cache-Control: no-storeAuthenticated responses are never cached by browsers or proxies.
WWW-AuthenticateOn 401/403: RFC 6750 Bearer challenge explaining what is wrong.
Example 200 headersHTTP
HTTP/2 200
content-type: application/json
x-request-id: 3b0f6c1e-8a2d-4f7e-9d61-2c5a7e0b9f14
ratelimit-limit: 30
ratelimit-remaining: 27
ratelimit-reset: 41
x-ratelimit-limit: 30
x-ratelimit-remaining: 27
x-ratelimit-reset: 1790921741
x-quota-limit: 5000
x-quota-remaining: 4958
cache-control: no-store
x-api-version: 1.1.0

Errors

Errors use RFC 9457 problem details (application/problem+json). Each has a stable type link, a human detail and the request_id. No stack traces, SQL or internal messages are ever returned.

400Bad Request#validation

Unknown, duplicated, wrongly typed or out-of-range query parameter.

Body
{
  "type": "https://pulse.krishnamuduli.co.in/docs#error-validation",
  "title": "Bad Request",
  "status": 400,
  "detail": "One or more query parameters are invalid.",
  "instance": "/api/v1/incidents",
  "request_id": "7f1c…",
  "errors": [
    {
      "param": "limit",
      "message": "Must be an integer between 1 and 200."
    },
    {
      "param": "debug",
      "message": "Unknown parameter. Allowed: limit, offset, …"
    }
  ]
}

401Unauthorized#unauthorized

No key, malformed header, or a key that is invalid, expired or revoked (one message for all, by design).

WWW-Authenticate: Bearer realm="pulse", error="invalid_token", …

Body
{
  "type": "https://pulse.krishnamuduli.co.in/docs#error-unauthorized",
  "title": "Unauthorized",
  "status": 401,
  "detail": "API key is invalid, expired or revoked.",
  "instance": "/api/v1/incidents",
  "request_id": "7f1c…"
}

403Forbidden#insufficient-scope

The key is valid but lacks the scope this endpoint needs.

WWW-Authenticate: Bearer realm="pulse", error="insufficient_scope", scope="read:kev"

Body
{
  "type": "https://pulse.krishnamuduli.co.in/docs#error-insufficient-scope",
  "title": "Forbidden",
  "status": 403,
  "detail": "This API key lacks the \"read:kev\" scope.",
  "instance": "/api/v1/kev",
  "request_id": "7f1c…",
  "required_scope": "read:kev",
  "key_scopes": [
    "read:iocs"
  ]
}

429Too Many Requests#rate-limited

Per-key per-minute limit exceeded.

Retry-After: 42 RateLimit-Limit: 30 RateLimit-Remaining: 0 RateLimit-Reset: 42

Body
{
  "type": "https://pulse.krishnamuduli.co.in/docs#error-rate-limited",
  "title": "Too Many Requests",
  "status": 429,
  "detail": "Rate limit of 30 requests per minute exceeded.",
  "instance": "/api/v1/iocs",
  "request_id": "7f1c…",
  "limit": 30,
  "window": "1m"
}

429Too Many Requests#quota-exceeded

Monthly request quota used up.

Body
{
  "type": "https://pulse.krishnamuduli.co.in/docs#error-quota-exceeded",
  "title": "Too Many Requests",
  "status": 429,
  "detail": "Monthly quota of 5000 requests exhausted. Resets 2026-11-01T00:00:00.000Z.",
  "request_id": "7f1c…",
  "quota": 5000
}

429Too Many Requests#too-many-failed-auth

More than 20 failed authentications from one client in a minute (brute-force protection).

Body
{
  "type": "https://pulse.krishnamuduli.co.in/docs#error-too-many-failed-auth",
  "title": "Too Many Requests",
  "status": 429,
  "detail": "Too many failed authentication attempts from this client. Retry after 37 seconds.",
  "request_id": "7f1c…"
}

500Internal Server Error#internal

Unexpected failure. No internals are exposed; quote request_id to support.

Body
{
  "type": "https://pulse.krishnamuduli.co.in/docs#error-internal",
  "title": "Internal Server Error",
  "status": 500,
  "detail": "Unexpected error. Quote the request_id when contacting support.",
  "request_id": "7f1c…"
}

503Service Unavailable#unavailable

A dependency (rate limiter / database) is temporarily unavailable. Requests fail closed.

Body
{
  "type": "https://pulse.krishnamuduli.co.in/docs#error-unavailable",
  "title": "Service Unavailable",
  "status": 503,
  "detail": "Rate limiter unavailable. Try again shortly.",
  "request_id": "7f1c…"
}

SDK snippets with retry & backoff

import os, time, requests

BASE = "https://pulse.krishnamuduli.co.in/api/v1"
S = requests.Session()
S.headers["Authorization"] = f"Bearer {os.environ['PULSE_API_KEY']}"   # keep keys in env/secret store

def get(path, **params):
    for attempt in range(5):
        r = S.get(f"{BASE}{path}", params=params, timeout=15)
        if r.status_code == 429:                       # honour Retry-After
            time.sleep(int(r.headers.get("Retry-After", 2 ** attempt)))
            continue
        if r.status_code >= 400:
            p = r.json()                               # RFC 9457 problem
            raise RuntimeError(f"{p['status']} {p['title']}: {p['detail']} (request_id={p['request_id']})")
        return r.json()
    raise RuntimeError("rate limited too many times")

# Page through all critical India incidents
offset = 0
while offset is not None:
    page = get("/incidents", country="IN", severity="Critical", limit=200, offset=offset)
    for i in page["data"]:
        print(i["created_at"], i["title"])
    offset = page["meta"]["next_offset"]

Security controls (OWASP API Top 10, 2023)

RiskControl in this API
API1 Broken Object Level AuthorizationData is read-only intelligence with no per-user objects; a key can only read its own metadata (/me). Responses use explicit field lists.
API2 Broken AuthenticationHashed (SHA-256) keys with a fixed format; one generic message for unknown/expired/revoked keys; 20 failed attempts/min per client → 429; expiry and revocation; constant-time secret comparison for webhooks and cron.
API3 Broken Object Property Level AuthorizationNo SELECT *: every endpoint returns an allow-listed set of fields. Internal columns (raw feed payloads with attacker .onion links, verification flags) are never exposed.
API4 Unrestricted Resource ConsumptionPer-key per-minute rate limit and monthly quota, capped page sizes and offsets, 429 + Retry-After. Internal search/export are limited per client.
API5 Broken Function Level AuthorizationScopes per endpoint (403 insufficient_scope). Key management is SQL-only (not exposed over HTTP); scheduled jobs need a secret.
API6 Unrestricted Access to Sensitive Business FlowsPayments: price fixed on the server, plan taken from the server-created order, webhook HMAC verified in constant time, each event processed once.
API7 Server Side Request ForgeryThe API never fetches user-supplied URLs. Ingestion only calls a fixed allow-list of feeds with timeouts.
API8 Security MisconfigurationDatabase row-level security with no anonymous reads; CSP, X-Frame-Options, nosniff, Referrer-Policy, Permissions-Policy, HSTS; no X-Powered-By; Cache-Control: no-store; RFC 9457 errors with no stack traces.
API9 Improper Inventory ManagementOpenAPI 3.1 spec generated from the code (single source of truth), versioned paths (/v1), changelog, legacy plaintext keys retired.
API10 Unsafe Consumption of APIsThird-party feed data is validated and sanitised; .onion links are dropped; headlines sent to the AI model are fenced as untrusted data (prompt-injection defence).

Audit log

Every API call is logged with request ID, key prefix, path, status, user agent and a salted IP hash (no raw IPs).

Reporting a vulnerability

See /.well-known/security.txt (RFC 9116). Please report privately and allow time to fix.

Data handling

IOC values are live malicious indicators: never open them. Ransomware entries are attacker claims, not confirmed breaches.

Postman demo guide

Setup (5 minutes)

  1. Download the collection → Postman → Import. (Or import openapi.json to generate requests from the spec.)
  2. In Supabase SQL, create three keys:select create_api_key('Demo – Postman', 'b2b'); select create_api_key('IOC-only demo', 'b2b', array['read:iocs']); select create_api_key('Rate-limit demo', 'b2b', null, 5);
  3. Open the collection → Variables → paste them into apiKey, scopedApiKey, rateLimitApiKey. Save.
  4. Run folder 1 · Endpoints → all green: data plus rate-limit headers.
  5. Run folder 2 · Security tests in the Collection Runner (request 12 with 10 iterations) for a pass/fail report.
  6. Show the trail: select * from api_request_log order by created_at desc limit 20;

Suggested talk flow

  1. Recon: DevTools → the dashboard bundle contains a public Supabase key (that's normal; it's meant to be public).
  2. Exploit (before): that key could read every table with public RLS, so the paid API could be bypassed (request 13).
  3. Business-logic bugs: valid keys were rejected and payments didn't upgrade plans: security bugs are revenue bugs.
  4. Fix: lock RLS, server-side reads, hashed scoped keys, rate limiting, strict validation, headers.
  5. Verify: run the security folder live; show 401/403/400/429 with problem+json and the headers test.
  6. Bonus (LLM): AI brief headlines are fenced as untrusted data against prompt injection.

Security test suite: expected results

#RequestExpected nowBefore v1.1
01No API key401 + WWW-Authenticate: BearerBefore: 401 (same)
02Malformed key ' OR 1=1--401, rejected by format checkBefore: 403
03Well-formed unknown key401, generic messageBefore: 403 (and valid keys also got 403)
04IOC-only key calls /kev403 insufficient-scope, names required scopeBefore: no scopes existed
05Unknown params ?debug=true&admin=1400 listing allowed paramsBefore: silently ignored
06?limit=100000400 field errorBefore: capped silently at 1000
07?severity=critical400 (case-sensitive allow-list)Before: empty 200
08SQL-injection text in actor400 (allow-listed charset)Before: passed to ILIKE
09Wildcard %%% in malware_family400Before: full-table wildcard scan
10?limit=5&limit=500 (HPP)400 duplicate parameterBefore: last value won
11?from=2026-13-45400 date formatBefore: 500 crash
126+ calls/min with the 5/min key429 + Retry-After, RateLimit-Remaining: 0Before: unlimited
13Supabase REST with the public keyNo data ([] or 401)Before: all 471 incidents
HSecurity headers on /docsCSP, XFO DENY, nosniff, Referrer-Policy, Permissions-Policy, HSTS, no X-Powered-ByBefore: HSTS only

Changelog

v1.1.02026-10-02

  • Security: API keys are now hashed (SHA-256), scoped, expiring and revocable; format ctp_live_<48 hex>.
  • Security: per-key rate limits and monthly quotas are enforced, with RateLimit-* and Retry-After headers.
  • Security: brute-force protection: >20 failed authentications per minute from one client → 429.
  • Security: strict validation: unknown/duplicate parameters, bad types and ranges return 400 with per-field errors.
  • Security: errors use RFC 9457 problem+json with request_id; no internal details are exposed.
  • Security: every request is written to an audit log (key prefix, path, status, hashed IP).
  • Security: direct database access with the public key is closed; data is served only through this API.
  • New endpoints: /api/v1/kev, /api/v1/ransomware-victims, /api/v1/me, /api/v1/health, /api/v1/openapi.json.
  • Changed: an invalid key now returns 401 (was 403); 403 now means "valid key, missing scope".
  • Changed: list responses include pagination (total, offset, next_offset).

v1.0.02026-04-02

  • Initial release: /incidents, /cert-alerts, /iocs with Bearer API keys.

Versioning: breaking changes get a new path (/v2). Deprecated versions announce a sunset date with the Deprecation and Sunset headers at least 90 days ahead.