CyberKit

Scheduled Task Abuse

Also called Cron Abuse, Scheduled Job.

Using the OS task scheduler to run or relaunch attacker code.

What it is

Abusing built-in job schedulers, such as Windows Task Scheduler or cron, to execute code at a chosen time or trigger. Tasks can run with elevated rights and survive reboots, serving execution, persistence, or privilege goals.

Why it matters

Scheduled tasks are a favored persistence and execution mechanism because they are native, flexible, and easy to overlook among thousands of legitimate jobs. Task creation events and the task store itself are high-value artifacts during eradication.

In practice

A newly created task that launches a script every morning is found re-establishing the attacker's foothold after each cleanup attempt.

What to look for

  • New tasks in event ID 4698 or under the Tasks folders that run from user-writable paths.
  • Tasks that launch script hosts, encoded commands or random-looking file names.
  • Tasks created remotely right after a network logon.

Common mistake

Only checking the task name. Attackers name tasks after real updaters, so read the action and the path it runs.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Atomic Red Team Open source

    Small, scripted tests mapped to ATT&CK techniques, used to check whether a detection fires.

  • ATT&CK Navigator Open source

    Lays techniques out on the ATT&CK matrix so teams can mark coverage, gaps and threat profiles.

  • Microsoft Defender for Endpoint Commercial

    Tags its alerts with the ATT&CK techniques it observed on the host.

  • Sysmon Free

    Supplies the host telemetry that most technique detections are written against. Our notes.

ATT&CK techniques

Read next

Sources