Detection rules › Splunk

ESXi System Clock Manipulation

Status
production
Severity
medium
Group by
delta, dest, direction, epoch_time, original_time_str, stepped_to_str
Author
Raven Tait, Splunk
Source
github.com/splunk/security_content

This detection identifies a significant change to the system clock on an ESXi host, which may indicate an attempt to manipulate timestamps and evade detection or forensic analysis

Known false positives

  • Limited false positives in most environments, however tune as needed

MITRE ATT&CK coverage

Rule body

name: ESXi System Clock Manipulation
id: 910df401-b215-4675-88c5-2ad7b06d82a5
version: 4
creation_date: '2025-07-11'
modification_date: '2026-05-13'
author: Raven Tait, Splunk
status: production
type: TTP
description: This detection identifies a significant change to the system clock on an ESXi host, which may indicate an attempt to manipulate timestamps and evade detection or forensic analysis
data_source:
    - VMWare ESXi Syslog
search: '`esxi_syslog` Message="*NTPClock*" AND Message="*system clock stepped*" | rex field=_raw "stepped to (?<epoch_time>\d+\.\d+),.+delta\s(?<delta>\d+)\s" | rex field=_raw "Z (?<dest>[\w\.]+)\s" | eval epoch_time=tonumber(epoch_time) | eval delta=tonumber(delta) | eval event_time=round(_time, 0) | eval direction=if(epoch_time < event_time, "backward", "forward") | eval original_time=if(direction=="backward", epoch_time + delta, epoch_time - delta) | eval stepped_to_str=strftime(epoch_time, "%Y-%m-%d %H:%M:%S") | eval original_time_str=strftime(original_time, "%Y-%m-%d %H:%M:%S") | stats min(_time) as firstTime max(_time) as lastTime count by dest direction original_time_str stepped_to_str epoch_time delta | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `esxi_system_clock_manipulation_filter`'
how_to_implement: This is based on syslog data generated by VMware ESXi hosts. To implement this search, you must configure your ESXi systems to forward syslog output to your Splunk deployment. These logs must be ingested with the appropriate Splunk Technology Add-on for VMware ESXi Logs, which provides field extractions and CIM compatibility.
known_false_positives: Limited false positives in most environments, however tune as needed
finding:
    title: Large time change on ESXi host $dest$.
    entity:
        field: dest
        type: system
        score: 50
analytic_story:
    - ESXi Post Compromise
    - Black Basta Ransomware
asset_type: Infrastructure
mitre_attack_id:
    - T1070.006
product:
    - Splunk Enterprise
    - Splunk Enterprise Security
    - Splunk Cloud
category: application
security_domain: endpoint

Stages and Predicates

Stage 1: search

`esxi_syslog` Message="*NTPClock*" AND Message="*system clock stepped*"

Stage 2: rex

| rex field=_raw "stepped to (?<epoch_time>\d+\.\d+),.+delta\s(?<delta>\d+)\s"

Stage 3: rex

| rex field=_raw "Z (?<dest>[\w\.]+)\s"

Stage 4: eval

| eval epoch_time=tonumber(epoch_time)

Stage 5: eval

| eval delta=tonumber(delta)

Stage 6: eval

| eval event_time=round(_time, 0)

Stage 7: eval

| eval direction=if(epoch_time < event_time, "backward", "forward")
direction =
ifepoch_time < event_time"backward"
else"forward"

Stage 8: eval

| eval original_time=if(direction=="backward", epoch_time + delta, epoch_time - delta)

Stage 9: eval

| eval stepped_to_str=strftime(epoch_time, "%Y-%m-%d %H:%M:%S")

Stage 10: eval

| eval original_time_str=strftime(original_time, "%Y-%m-%d %H:%M:%S")

Stage 11: stats

| stats min(_time) as firstTime max(_time) as lastTime count by dest direction original_time_str stepped_to_str epoch_time delta

Stage 12: search

| `security_content_ctime(firstTime)`

Stage 13: search

| `security_content_ctime(lastTime)`

Stage 14: search

| `esxi_system_clock_manipulation_filter`

Indicators

These rows show field, operator, and value matches.

FieldKindValuesSearch
Messageeq
  • "*NTPClock*"
  • "*system clock stepped*"
field:"Message" kind:eq
sourcetypein
  • vmw-syslog
  • vmware:esxlog*
field:"sourcetype" kind:in