Back to catalog
Static reviewDevelopment

Skill dossier

hunting-for-suspicious-scheduled-tasks

Source declaration

Hunts for adversary persistence and execution via Windows scheduled tasks (T1053.005) by analyzing Security Event ID 4698 task-creation events, suspicious task properties, and unusual execution patterns from schtasks.exe/at.exe. Use after detecting schtasks or at.exe in process creation logs, during incident response to enumerate persistence on compromised hosts, or when Event ID 4698 fires for an unusual task.

The author's original description, preserved in English. It describes intent, not verified performance.

Hunts for adversary persistence and execution via Windows scheduled tasks (T1053.005) by analyzing Security Event ID 4698 task-creation events, suspicious task properties, and unusual execution patterns from schtasks.exe/at.exe. Use after detecting schtasks or at.exe in process creation logs, during incident response to enumerate persistence on compromised hosts, or when Event ID 4698 fires for an unusual task.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Hunts for adversary persistence and execution via Windows scheduled tasks (T1053.005) by analyzing Security Event ID 4698 task-creation events, suspicious task properties, and unusual execution patterns from schtasks.exe/at.exe. Use after detecting schtasks or at.exe in process creation logs, during incident response to enumerate persistence on compromised hosts, or when Event ID 4698 fires for an unusual task. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/hunting-for-suspicious-scheduled-tasks/SKILL.md:L47]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/hunting-for-suspicious-scheduled-tasks/SKILL.md:L1-L27]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
32.5 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/hunting-for-suspicious-scheduled-tasks/assets/template.mdReference786 B
skills/hunting-for-suspicious-scheduled-tasks/LICENSEOther11 KB
skills/hunting-for-suspicious-scheduled-tasks/references/api-reference.mdReference1.9 KB
skills/hunting-for-suspicious-scheduled-tasks/references/standards.mdReference1.4 KB
skills/hunting-for-suspicious-scheduled-tasks/references/workflows.mdReference1.2 KB
skills/hunting-for-suspicious-scheduled-tasks/scripts/agent.pyScript6.8 KB
skills/hunting-for-suspicious-scheduled-tasks/scripts/process.pyScript4.7 KB
skills/hunting-for-suspicious-scheduled-tasks/SKILL.mdInstruction4.8 KB

SKILL.md frontmatter

{
  "name": "hunting-for-suspicious-scheduled-tasks",
  "description": "Hunts for adversary persistence and execution via Windows scheduled tasks (T1053.005) by analyzing Security Event ID 4698 task-creation events, suspicious task properties, and unusual execution patterns from schtasks.exe/at.exe. Use after detecting schtasks or at.exe in process creation logs, during incident response to enumerate persistence on compromised hosts, or when Event ID 4698 fires for an unusual task.",
  "domain": "cybersecurity",
  "subdomain": "threat-hunting",
  "tags": [
    "threat-hunting",
    "scheduled-tasks",
    "persistence",
    "mitre-t1053-005",
    "windows",
    "endpoint-detection"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "DE.CM-01",
    "DE.AE-02",
    "DE.AE-07",
    "ID.RA-05"
  ],
  "mitre_attack": [
    "T1046",
    "T1057",
    "T1082",
    "T1083",
    "T1547"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Enumerate All Scheduled Tasks: Collect complete task inventory from target systems using `schtasks /query /fo CSV /v` or `Get-ScheduledTask` PowerShell cmdlet.

    Source-described action candidate under “Workflow”; not verified execution.

  4. 04
    Action

    Monitor Task Creation Events: Track Event ID 4698 for new task creation, correlating with the creating process and user account context.

    Source-described action candidate under “Workflow”; not verified execution.

  5. 05
    Action

    Analyze Task Actions: Examine what each task executes. Flag tasks running scripts (PowerShell, cmd, wscript), binaries from user-writable paths (TEMP, AppData, Downloads), or encoded/obfuscated commands.

    Source-described action candidate under “Workflow”; not verified execution.

  6. 06
    Action

    Check Task Triggers: Review trigger conditions. Tasks triggered by system startup, user logon, or short intervals (1-5 minutes) warrant investigation.

    Source-described action candidate under “Workflow”; not verified execution.

Inspect all extracted workflow candidates (17 candidate steps)
  1. 07
    Action

    Identify Hidden or Disguised Tasks: Hunt for tasks with names mimicking legitimate Windows tasks, tasks with Security Descriptor modifications hiding them from standard enumeration, or tasks stored in non-standard registry locations.

    Source-described action candidate under “Workflow”; not verified execution.

  2. 08
    Action

    Correlate with Process Execution: Match scheduled task execution events with process creation logs to confirm what actually runs.

    Source-described action candidate under “Workflow”; not verified execution.

  3. 09
    Action

    Baseline and Diff: Compare current task inventory against known-good baselines to identify new, modified, or unexpected tasks.

    Source-described action candidate under “Workflow”; not verified execution.

  4. 10
    Action

    Detection Queries

    Source-described action candidate under “Detection Queries”; not verified execution.

  5. 11
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  6. 12
    Action

    Cobalt Strike Persistence: Creates scheduled tasks via schtasks.exe to execute PowerShell download cradles at user logon intervals.

    Source-described action candidate under “Common Scenarios”; not verified execution.

  7. 13
    Action

    Ransomware Staging: Task created to run encryption payload at a future time, often during off-hours for maximum impact.

    Source-described action candidate under “Common Scenarios”; not verified execution.

  8. 14
    Action

    Hidden Task via SD Modification: Attacker modifies Security Descriptor of scheduled task to hide it from normal enumeration while maintaining execution.

    Source-described action candidate under “Common Scenarios”; not verified execution.

  9. 15
    Action

    COM Handler Abuse: Task uses COM handler rather than direct executable path, making action inspection more complex.

    Source-described action candidate under “Common Scenarios”; not verified execution.

  10. 16
    Action

    Lateral Movement via Tasks: Remote scheduled task creation using `schtasks /create /s REMOTEHOST` for execution on other systems.

    Source-described action candidate under “Common Scenarios”; not verified execution.

  11. 17
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

22 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

9 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 9 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

13 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 13 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/hunting-for-suspicious-scheduled-tasks/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/hunting-for-suspicious-scheduled-tasks/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/hunting-for-suspicious-scheduled-tasks
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.