Skip to content

Malicious Redirect Behavior

It refers to the automatic forwarding of a user or system request from one domain to another destination. Redirects can occur through HTTP response headers, JavaScript scripts, meta refresh tags, or chained links. While many redirects are legitimate, malicious infrastructures often use them to conceal their true targets or to evade reputation-based filtering.

Also surfaces as:
Risky Redirect ActivityRedirect to a Restricted DomainDirect-to-IP RedirectRedirect
Analyst Q&A

What this signal answers

Three questions every analyst asks before acting on this signal.

What it detects01

What does 'Redirect Behavior' mean in SOC or domain analysis?

It refers to the automatic forwarding of a user or system request from one domain to another destination. Redirects can occur through HTTP response headers, JavaScript scripts, meta refresh tags, or chained links. While many redirects are legitimate, malicious infrastructures often use them to conceal their true targets or to evade reputation-based filtering.

Why it matters02

Why is redirect behavior important for security analysts?

Because redirect patterns are commonly abused in phishing, malvertising, and exploit delivery chains. Threat actors may use multiple intermediate redirects to hide the origin or to deliver a final malicious payload only after several hops. Detecting and mapping redirect paths can reveal the full infection chain and infrastructure relationships.

How analysts use it03

Why are Direct-to-IP redirects especially suspicious?

Redirects that point directly to raw IP addresses instead of domain names are highly unusual for legitimate web services. Threat actors use them to bypass domain-based filters, obscure attribution, or directly connect victims to command-and-control (C2) servers or phishing infrastructure.

Often paired with:block_domain
Evidence shape

What Malicious Redirect Behavior 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": "redirect",
  "name": "Malicious Redirect Behavior",
  "group": "http_crawling_history",
  "subgroup": "web_behavior_structure",
  "direction": "malicious",
  "evidence": {
    "url_shortener_chain": false,
    "auto_refresh_seconds": null,
    "direct_ip_link": false,
    "browser_interaction_required": true
  }
}
See in API reference
Siblings

Peers in Web Behavior & Structure

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

Injected Iframe

An injected iframe refers to an HTML frame embedded within a web page that loads content from an external or malicious d

MaliciousCore
Direct Connection to an IP Address

It refers to the action of accessing a resource using a direct IP address instead of a domain name. Threat actors often

Malicious
JavaScript-based Redirect

It refers to a redirect mechanism implemented within a webpage using JavaScript code instead of standard HTTP response h

Malicious
Suspicious Auto Page Refresh Activity

It indicates that the domain or web page automatically reloads itself after a certain interval without user interaction.

Malicious
Show 3 more in Web Behavior & Structure
In the wild

See Malicious Redirect Behavior 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 Malicious Redirect Behavior. See real IOCs this signal caught and the verdicts the engine returned.
Verdicts ✓

Start free, in five minutes

100 IOCs/day on the free tier, LLM layer included. No card required.