Join our Newsletter — 33% off our NHI Course
Threats, Abuse & Incident Response

Delayed Redirect

← Back to Glossary
By NHI Mgmt Group Updated November 5, 2026 Domain: Threats, Abuse & Incident Response

A delayed redirect is a script that waits before sending the user to a malicious destination. The delay helps attackers bypass static analysis because the harmful action happens after the initial scan window rather than during delivery.

How delayed redirects work

A delayed redirect is a time-based evasion technique, not just a benign delay. The script waits long enough for a scanner, sandbox, or automated browser to finish its initial pass, then sends the user to a destination that would have been blocked if it had appeared immediately.

This pattern often relies on simple JavaScript timing, but the exact implementation matters less than the effect: the page looks harmless during the first few seconds, which can defeat tools that only evaluate the first page load or ignore delayed execution.

Why attackers use delayed redirects

Attackers use delayed redirects to separate delivery from detonation. The initial page can host benign content, a decoy, or a minimal loader, while the malicious destination is only revealed after the delay or after a user interaction that automated analysis may not reproduce.

That makes the technique useful in phishing, malware delivery, traffic distribution, and affiliate abuse. It can also help attackers rotate destinations, test security controls, or conditionally route only some visitors to the harmful site.

Because the redirect is time-sensitive, it can be harder to catch with static rules alone. The malicious domain, URL path, or payload may never appear in the first fetch, which reduces the chance that a simple crawler or signature match will flag the page.

Security implications for defenders

The main security problem is that delayed redirects exploit a visibility gap between page delivery and full behavioural inspection. If defenders only inspect the first response, they may miss the second-stage destination and the activity that follows it.

Detection works best when analysis observes time, script execution, DOM changes, and outbound navigation over a longer window. Security teams should treat delayed redirects as a behavioural indicator, not merely a content issue, because the real risk is the destination and what happens there.

Controls that improve inspection depth include browser instrumentation, detonation with sufficient dwell time, URL reputation checks after execution, and policy controls that constrain automatic redirection from untrusted sources. Where users are involved, awareness also matters because a delay can make a malicious page appear more legitimate than it is.

How to investigate and respond

When a delayed redirect is suspected, compare the first response with the full execution trace. Look for timers, conditional branches, hidden scripts, or delayed location changes that only occur after a threshold is reached or after a user event.

Investigators should capture the full redirect chain, the final landing page, and any network requests made after the wait period. If the redirect led to credential theft, malware download, or session capture, the incident should be handled as a compromise path, not as a simple web nuisance.

For analysts, the key question is whether the delay is merely cosmetic or whether it is being used to evade scanning. If the latter is true, the page should be treated as hostile even when the initial content looks harmless.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while NIST CSF 2.0 and OWASP ASVS set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1204 — User ExecutionDelayed redirects rely on user interaction or browser execution to reach the malicious destination.
T1105 — Ingress Tool TransferDelayed redirects often deliver or stage a second-stage payload after the wait period.
Recommendation — Correlate delayed navigation with user-execution paths and hunt for the follow-on destination. Inspect delayed redirect chains for staged payload delivery and downstream transfers.
NIST CSF 2.0DE.CM-01 — Continuous MonitoringBehavioural monitoring is needed to observe delayed script execution and later navigation.
Recommendation — Extend monitoring windows so delayed navigation and post-load behaviour are captured.
OWASP ASVSV16 — Security Logging and Error HandlingRedirect behaviour should be logged so delayed navigation can be reviewed and investigated.
Recommendation — Log redirect events and preserve execution traces for later incident review.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org