hunting-for-scheduled-task-persistence

Hunt for adversary persistence via Windows Scheduled Tasks by analyzing task creation events, suspicious task actions, and unusual scheduling patterns.

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

8.6K

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/hunting-for-scheduled-task-persistence

0

installs

0

this week

8.6K

stars

Installation Guide

How to use hunting-for-scheduled-task-persistence on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add hunting-for-scheduled-task-persistence
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/hunting-for-scheduled-task-persistence

Fetches hunting-for-scheduled-task-persistence from mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/hunting-for-scheduled-task-persistence

Restart Cursor to activate hunting-for-scheduled-task-persistence. Access via /hunting-for-scheduled-task-persistence in your agent's command palette.

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

Documentation

name
hunting-for-scheduled-task-persistence
description
Hunt for adversary persistence via Windows Scheduled Tasks by analyzing task creation events, suspicious task actions, and unusual scheduling patterns.
domain
cybersecurity
subdomain
threat-hunting
tags
- threat-hunting - mitre-attack - scheduled-tasks - persistence - t1053 - proactive-detection
version
'1.0'
author
mahipal
license
Apache-2.0
d3fend_techniques
- Execution Isolation - Process Termination - Hardware-based Process Isolation - Platform Monitoring - Process Suspension
nist_csf
- DE.CM-01 - DE.AE-02 - DE.AE-07 - ID.RA-05

Hunting For Scheduled Task Persistence

When to Use

  • When proactively hunting for indicators of hunting for scheduled task persistence in the environment
  • After threat intelligence indicates active campaigns using these techniques
  • During incident response to scope compromise related to these techniques
  • When EDR or SIEM alerts trigger on related indicators
  • During periodic security assessments and purple team exercises

Prerequisites

  • EDR platform with process and network telemetry (CrowdStrike, MDE, SentinelOne)
  • SIEM with relevant log data ingested (Splunk, Elastic, Sentinel)
  • Sysmon deployed with comprehensive configuration
  • Windows Security Event Log forwarding enabled
  • Threat intelligence feeds for IOC correlation

Workflow

  1. Formulate Hypothesis: Define a testable hypothesis based on threat intelligence or ATT&CK gap analysis.
  2. Identify Data Sources: Determine which logs and telemetry are needed to validate or refute the hypothesis.
  3. Execute Queries: Run detection queries against SIEM and EDR platforms to collect relevant events.
  4. Analyze Results: Examine query results for anomalies, correlating across multiple data sources.
  5. Validate Findings: Distinguish true positives from false positives through contextual analysis.
  6. Correlate Activity: Link findings to broader attack chains and threat actor TTPs.
  7. Document and Report: Record findings, update detection rules, and recommend response actions.

Key Concepts

ConceptDescription
T1053.005Scheduled Task
T1053.003Cron
T1053.002At

Tools & Systems

ToolPurpose
CrowdStrike FalconEDR telemetry and threat detection
Microsoft Defender for EndpointAdvanced hunting with KQL
Splunk EnterpriseSIEM log analysis with SPL queries
Elastic SecurityDetection rules and investigation timeline
SysmonDetailed Windows event monitoring
VelociraptorEndpoint artifact collection and hunting
Sigma RulesCross-platform detection rule format

Common Scenarios

  1. Scenario 1: Cobalt Strike persistence via schtasks creating periodic beacon
  2. Scenario 2: Ransomware scheduled task for re-execution after reboot
  3. Scenario 3: APT encoded PowerShell task running every 30 minutes
  4. Scenario 4: Insider task to periodically copy sensitive files

Output Format

Hunt ID: TH-HUNTIN-[DATE]-[SEQ]
Technique: T1053.005
Host: [Hostname]
User: [Account context]
Evidence: [Log entries, process trees, network data]
Risk Level: [Critical/High/Medium/Low]
Confidence: [High/Medium/Low]
Recommended Action: [Containment, investigation, monitoring]

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Steps

  1. 1Install skill using provided installation command
  2. 2Test with simple use case relevant to your work
  3. 3Evaluate output quality and relevance
  4. 4Iterate on prompts to improve results
  5. 5Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use when

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid when

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Related Skills

Reviews

4.551 reviews
  • H
    Hana WhiteDec 28, 2024

    hunting-for-scheduled-task-persistence fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • C
    Camila ChawlaDec 28, 2024

    Keeps context tight: hunting-for-scheduled-task-persistence is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • S
    Shikha MishraDec 24, 2024

    hunting-for-scheduled-task-persistence has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • G
    Ganesh MohaneDec 20, 2024

    I recommend hunting-for-scheduled-task-persistence for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • M
    Mateo MenonDec 8, 2024

    We added hunting-for-scheduled-task-persistence from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • M
    Mateo BansalNov 27, 2024

    hunting-for-scheduled-task-persistence fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • M
    Mateo ChawlaNov 19, 2024

    We added hunting-for-scheduled-task-persistence from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • S
    Soo SmithNov 15, 2024

    Keeps context tight: hunting-for-scheduled-task-persistence is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • S
    Sakshi PatilNov 11, 2024

    Useful defaults in hunting-for-scheduled-task-persistence — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • S
    Sofia FloresOct 18, 2024

    Registry listing for hunting-for-scheduled-task-persistence matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 51

1 / 6

Discussion

Comments — not star reviews
  • No comments yet — start the thread.