Skip to content
cccskills
FreePublished on GitHub

scoping-an-incident-from-a-single-indicator

Expands one indicator into the full scope of an incident: pivoting across data sources to find related hosts, accounts, and infrastructure, building a timeline, and bounding what is and is not affected. Activates for requests to scope an incident, pivot from a single IOC, or determine the blast radius of a detection.

The English summary is being prepared. Showing the original description.

See how to install

Files included (4)

  • SKILL.md3.0 KB
  • LICENSE340 B
  • references/api-reference.md1.3 KB
  • scripts/analyst.py2.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Scoping an Incident from a Single Indicator

When to Use

  • A detection fired on one indicator (a hash, IP, domain, or account) and you must find the full extent of the activity.
  • You need to bound the incident — which hosts, accounts, and infrastructure are involved — before containment.
  • You are building an investigative timeline from a single starting point.

Do not use premature containment on the first indicator alone — acting before scoping can tip off the adversary and leave footholds you have not yet found.

Prerequisites

  • Access to relevant data sources (EDR, proxy, DNS, auth logs) and the pivoting/enrichment skills.

Workflow

Step 1: Characterize the seed indicator

Establish what the indicator is, when it was first/last seen, and on which host/account it appeared.

Step 2: Pivot to related artifacts

Expand outward: the file's other hosts, the IP's other connections, the account's other logons, the domain's other resolvers. Each pivot yields new indicators to pivot again.

python scripts/analyst.py scope events.json --seed <sha256-or-ip>

Step 3: Build the timeline

Order all discovered events chronologically to reconstruct the activity and find the earliest sign (candidate patient zero / initial access).

Step 4: Bound the scope

Define affected vs. unaffected explicitly: list involved hosts/accounts/infrastructure and the evidence for inclusion, and note what was checked and cleared.

Step 5: Hand off to containment

Produce the scoped picture (entities, timeline, indicators) so containment is coordinated and complete rather than piecemeal.

Validation

  • Every included entity has explicit evidence tying it to the incident.
  • The timeline has a defensible earliest event (initial access candidate).
  • Cleared entities are documented, so scope is bounded, not open-ended.

Pitfalls

  • Containing the first host before pivoting, alerting the adversary and missing other footholds.
  • Pivoting only one hop and missing second-order related entities.
  • No timeline, so initial access and dwell time stay unknown.

References

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Reverses Android malware: unpacking APKs, decompiling DEX bytecode to readable Java, auditing the manifest for abused permissions and components, and locating dynamically loaded or native payloads. Activates for requests to analyze an APK, decompile DEX, or investigate a suspicious Android app.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes API call traces from a sandbox or API monitor (JSON) to group calls by category, reconstruct high-level behaviors (process injection, file drops, network, crypto), and flag suspicious call sequences. Activates for requests to analyze an API trace, interpret sandbox API logs, or identify behavior from Win32/Native API calls.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes Windows Authenticode signatures on PE files: checking for a signature, reading the signer certificate chain, detecting revoked/expired/stolen certs, and recognizing signature-stripping and catalog-signing abuse. Activates for requests to analyze a code signature, verify Authenticode, or assess signer trust on a PE.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes banking trojan webinject configurations to extract targeted institutions, injected JavaScript/HTML, and data-theft hooks, mapping the fraud workflow. Activates for requests to analyze banking trojan webinjects, parse a webinject config, or map targeted banks and credential-theft injections.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes Python-based malware packaged as PyInstaller/py2exe executables by detecting the packer, locating the embedded archive, and identifying bundled .pyc modules for extraction and decompilation. Activates for requests to analyze compiled Python malware, unpack a PyInstaller binary, or extract pyc modules from a frozen Python executable.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes cryptojacking/coinminer malware by extracting mining pool endpoints (stratum), wallet addresses, algorithm and miner identifiers (XMRig and forks), and persistence or resource-control settings from static strings and config. Activates for requests to analyze a cryptominer, extract mining pool and wallet IOCs, or identify coinminer configuration.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

See all skills by meltedinhex

Report a problem with this skill