Skip to content
NewVerdictIQ Connector is here. One Docker image enriches your DNS logs with verdicts inside your network and forwards them to your SIEM.Install guide

Suspicious CORS Exposure

It indicates weak or overly permissive CORS configurations such as wildcard origins, broad method or header allowances, origin mismatches, or timing exposure that increase attack surface but may also result from misconfiguration rather than explicit malicious intent.

Also surfaces as:
Known Malicious CORS Pattern
Analyst Q&A

What this signal answers

The questions every analyst asks before acting on this signal.

What it detects01

What does 'Suspicious CORS Exposure' indicate?

It indicates weak or overly permissive CORS configurations such as wildcard origins, broad method or header allowances, origin mismatches, or timing exposure that increase attack surface but may also result from misconfiguration rather than explicit malicious intent.

Why it matters02

What does 'Known Malicious CORS Pattern' mean?

It describes CORS configurations that match fingerprints seen in phishing kits, traffic brokers, malvertising chains, or credential-harvesting infrastructures, including credential-enabled wildcard origins and abuse-cluster-correlated patterns.

How analysts use it03

How should SOC analysts interpret this label?

This is a strong malicious-context signal. The higher sublabel significantly increases confidence in abuse, especially when correlated with risky cookie behavior, redirector chains, telemetry anomalies, or DNS instability.

Often paired with:block_domain
Evidence shape

What Suspicious CORS Exposure looks like in the response

A realistic shape of the entry the engine appends to the risk_signals array when this signal fires. Evidence keys are subgroup-default; per-signal overrides documented in the API reference.

json
{
  "slug": "http_cors_misconfiguration",
  "name": "Suspicious CORS Exposure",
  "group": "http_crawling_history",
  "subgroup": "http_header_behaviors",
  "direction": "malicious",
  "evidence": {
    "missing_security_headers": 4,
    "cors_origin": "*",
    "cors_credentials_allowed": true,
    "provider_type": "self_hosted",
    "risky_cookie_count": 2
  }
}
See in API reference
Siblings

Peers in HTTP Header Behaviors

12 other signals share the same subgroup. They detect related behaviors and often co-fire on the same IOC.

Weak or Misconfigured Security Headers

It indicates missing, weak, contradictory, or overly permissive security headers (such as CSP, HSTS, X-Frame-Options, Pe…

MaliciousCore
Basic Profiling Cookie Risk

It indicates that the site sets cookies issued by specific edge protection providers whose cookies appear far more often…

MaliciousCore
Suspicious Header Structure

It indicates abnormal HTTP header structures such as unusually minimal or dense header sets, odd ordering, unexpected pr…

MaliciousCore
Suspicious Redirector Behavior

It indicates abnormal HTTP redirection patterns such as instant refresh redirects, header-based redirects, forced interm…

MaliciousCore
Show 8 more in HTTP Header Behaviors
In the wild

See Suspicious CORS Exposure fire on real IOCs

The Verdict Gallery is a curated stream of real verdicts. Filter by this signal to see exactly which IOCs it caught, what other signals fired alongside it, and what the engine recommended.

Open Verdict Gallery
Pre-filtered to Suspicious CORS Exposure. See real IOCs this signal caught and the verdicts the engine returned.
Verdicts ✓

Start free, in five minutes

1,000 verdicts/month on the free tier, LLM layer included. No card required.