Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/hunting-scheduled-task-abuseDFIR and threat hunting

hunting-scheduled-task-abuse

⁨Hunts for malicious scheduled task persistence by analyzing task registration events⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/hunting-scheduled-task-abuse

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
2urKoj6LwE…5YUmmrBQ==The CLI checks the SHA-256 and the signature before it writes a file.
Packageb890f62d…3d809147
b890f62de013…91bc3d8091474 files · ⁦3.0 KB⁩
ScanMedium4 findings
  • command.persistenceSKILL.md:56
  • command.persistenceSKILL.md:74
  • Executable script shipped with the skillscripts/analyst.py
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-scheduled-task-abuse@da7600a

When to Use

  • You have task-registration events (4698) and/or schtasks.exe/at.exe process telemetry and want to detect persistence via malicious scheduled tasks.
  • You are investigating tasks that run scripts, encoded commands, or binaries from suspicious paths.

Do not use this to alert on all task creation — administration creates tasks routinely. Hunt on the action (script hosts, encoded commands, temp paths) and trigger context.

Prerequisites

  • Event ID 4698 (task registered) and/or process-creation telemetry for schtasks/at.

Workflow

Step 1: Hunt suspicious task actions

bash
python scripts/analyst.py hunt events.csv

Flags tasks whose action runs powershell -enc, mshta, wscript/cscript, cmd /c, or binaries from %TEMP%/%APPDATA%/Public, and schtasks /create command lines with the same.

Step 2: Assess triggers and hiding

Note logon/onstart triggers, very frequent intervals, and tasks hidden via Hidden flag or SD manipulation.

Step 3: Confirm

Distinguish legitimate software tasks from intrusion by author, path, and action content.

Step 4: Operationalize

Write a Sigma rule for task actions invoking script hosts or encoded commands.

Validation

  • Flags require a suspicious action/path, not task creation alone.
  • schtasks /create and 4698 registrations are both covered.
  • Findings map to ATT&CK T1053.005.

Pitfalls

  • Legitimate updater tasks (browsers, vendors) creating many tasks.
  • Tasks created via direct XML drop bypassing schtasks.exe telemetry.
  • Encoded commands hiding the true action.

References

  • See references/api-reference.md for the hunter.
  • ATT&CK T1053.005 and Event 4698 docs (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumCommand · command.persistenceSKILL.md:56
  2. MediumCommand · command.persistenceSKILL.md:74
  3. MediumFile · Executable script shipped with the skillscripts/analyst.py
  4. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600ab890f62dSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login