Operator On The Wire
Join
← Back to Knowledge Base
BLUE TEAM / THREAT HUNT / WINDOWS / EVASION

Timestomping

This note documents detection patterns related to Timestomping within Windows environments.


Direct Indicators

LogEvent IDMeaningForensic ValueNotes
Sysmon2File creation time changedCriticalPrimary timestomp detection event.
Sysmon11File createCriticalFile appears before timestamp alteration.
Security4663File accessHighFile touched during timestomp workflow.
Security4688Process creationCriticalDetects timestomp tooling.
Sysmon1Process creationCriticalBest lineage source for file tampering chain.
Sysmon23File deleteMediumCleanup after timestomp.

Indirect Indicators

IndicatorWhat To Look ForForensic ValueNotes
Timestamp older than surrounding MFT activityTimeline inconsistencyCriticalCore timestomp clue.
$STANDARD_INFORMATION vs $FILE_NAME mismatchNTFS timestamp divergenceCriticalHigh-confidence forensic signal.
File created then immediately timestamp alteredStrong malicious patternCriticalClassic attacker behavior.
Tool writes to payload after dropStrong sequenceCriticalHigh-value chain.
Multiple files share same fake timeBulk timestompHighCampaign clue.
Temp/AppData payload with old timestampStrong anomalyHighSuspicious artifact

Common Tools

ToolUsage
PowerShellSet file timestamps
timestomp.exeMetasploit style timestomp
cmd.exeCopy timestamp tricks
custom malwareAPI timestamp alteration

Relevant Artifacts

  • Sysmon Event IDs 2, 11, 1, 23
  • Security Event IDs 4663, 4688
  • MFT:
    • $STANDARD_INFORMATION
    • $FILE_NAME
  • USN Journal
  • Prefetch for timestomp tool
  • File metadata timeline

MITRE ATT&CK References

  • T1070.006 Timestomp

Decision Tree

  1. Which file altered?

    • Payload
    • Script
    • DLL
  2. Which timestamp changed?

    • Created
    • Modified
    • Accessed
  3. MFT mismatch present?

    • Yes
    • No
  4. Adjacent activity?

    • Drop
    • Execution
    • Archive
  5. Expand:

    • USN
    • MFT timeline
    • Parent process
  6. Scope:

    • Single file
    • Bulk timestomp
    • Campaign behavior

Example Detection Templates

KQL

Sysmon
| where EventID == 2
| project TimeGenerated, Computer, TargetFilename, CreationUtcTime, PreviousCreationUtcTime
SecurityEvent
| where EventID == 4688
| where CommandLine has_any ("timestomp","SetCreationTime")
| project TimeGenerated, Computer, CommandLine

EQL

file where event.code == "2"
sequence by host.name with maxspan=5m
  [ file where event.code == "11" ]
  [ file where event.code == "2" ]

Sigma

title: Timestomping Detection
id: 4a8c2f16-timestomp
status: experimental
description: Detects file creation time modification
references:
  - https://attack.mitre.org/
author: Vergil
date: 2026-03-07
logsource:
  product: windows
  service: sysmon
detection:
  selection:
    EventID: 2
  condition: selection
fields:
  - TargetFilename
  - CreationUtcTime
  - PreviousCreationUtcTime
falsepositives:
  - Rare legitimate software
level: high
tags:
  - attack.defense_evasion

Mitigation & Hardening

Control AreaMitigationEffectivenessNotes
Enable Sysmon 2Critical visibilityCriticalPrimary signal
Compare MFT attributesHigh-confidence validationCriticalStrong DFIR method
Preserve USN JournalCatch hidden editsHighValuable timeline
Alert on drop + timestompStrong sequenceCriticalHigh-confidence triage
File timeline baseliningDetect anomaliesHighValuable enrichment