Back to catalog
Static reviewDevelopment

Skill dossier

detecting-t1055-process-injection-with-sysmon

Source declaration

Detect process injection techniques (T1055) - including DLL injection, process hollowing, and APC injection - by analyzing Sysmon Event IDs 1, 7, 8, 10, and 25 for cross-process memory operations, remote thread creation, and anomalous DLL loads. Use when hunting defense-evasion activity that hides code inside legitimate processes, investigating an EDR alert on suspicious cross-process access, or validating Sysmon coverage for injection detection.

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

Detect process injection techniques (T1055) - including DLL injection, process hollowing, and APC injection - by analyzing Sysmon Event IDs 1, 7, 8, 10, and 25 for cross-process memory operations, remote thread creation, and anomalous DLL loads. Use when hunting defense-evasion activity that hides code inside legitimate processes, investigating an EDR alert on suspicious cross-process access, or validating Sysmon coverage for injection detection.

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.

Detect process injection techniques (T1055) - including DLL injection, process hollowing, and APC injection - by analyzing Sysmon Event IDs 1, 7, 8, 10, and 25 for cross-process memory operations, remote thread creation, and anomalous DLL loads. Use when hunting defense-evasion activity that hides code inside legitimate processes, investigating an EDR alert on suspicious cross-process access, or validating Sysmon coverage for injection detection. 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

  • Detecting T1055 Process Injection with Sysmon [Source statement; provisional, not tested. Evidence: skills/detecting-t1055-process-injection-with-sysmon/SKILL.md:L40]
  • Workflow [Source statement; provisional, not tested. Evidence: skills/detecting-t1055-process-injection-with-sysmon/SKILL.md:L59]
  • Splunk -- Suspicious ProcessAccess Patterns [Source statement; provisional, not tested. Evidence: skills/detecting-t1055-process-injection-with-sysmon/SKILL.md:L110]
  • KQL -- Process Injection via Remote Thread [Source statement; provisional, not tested. Evidence: skills/detecting-t1055-process-injection-with-sysmon/SKILL.md:L120]
  • Sigma Rule -- Process Injection Detection [Source statement; provisional, not tested. Evidence: skills/detecting-t1055-process-injection-with-sysmon/SKILL.md:L131]

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/detecting-t1055-process-injection-with-sysmon/SKILL.md:L1-L38]

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
39.7 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/detecting-t1055-process-injection-with-sysmon/assets/template.mdReference978 B
skills/detecting-t1055-process-injection-with-sysmon/LICENSEOther11 KB
skills/detecting-t1055-process-injection-with-sysmon/references/api-reference.mdReference2.7 KB
skills/detecting-t1055-process-injection-with-sysmon/references/standards.mdReference3.2 KB
skills/detecting-t1055-process-injection-with-sysmon/references/workflows.mdReference3 KB
skills/detecting-t1055-process-injection-with-sysmon/scripts/agent.pyScript5.4 KB
skills/detecting-t1055-process-injection-with-sysmon/scripts/process.pyScript5.9 KB
skills/detecting-t1055-process-injection-with-sysmon/SKILL.mdInstruction7.7 KB

SKILL.md frontmatter

{
  "name": "detecting-t1055-process-injection-with-sysmon",
  "description": "Detect process injection techniques (T1055) - including DLL injection, process hollowing, and APC injection - by analyzing Sysmon Event IDs 1, 7, 8, 10, and 25 for cross-process memory operations, remote thread creation, and anomalous DLL loads. Use when hunting defense-evasion activity that hides code inside legitimate processes, investigating an EDR alert on suspicious cross-process access, or validating Sysmon coverage for injection detection.",
  "domain": "cybersecurity",
  "subdomain": "threat-hunting",
  "tags": [
    "threat-hunting",
    "process-injection",
    "sysmon",
    "mitre-t1055",
    "defense-evasion",
    "dll-injection",
    "process-hollowing"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "d3fend_techniques": [
    "Executable Denylisting",
    "Execution Isolation",
    "File Metadata Consistency Validation",
    "Content Format Conversion",
    "File Content Analysis"
  ],
  "nist_csf": [
    "DE.CM-01",
    "DE.AE-02",
    "DE.AE-07",
    "ID.RA-05"
  ],
  "mitre_attack": [
    "T1055.001",
    "T1055.002",
    "T1055.003",
    "T1055.012"
  ]
}

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
    Action

    Detecting T1055 Process Injection with Sysmon

    Source-described action candidate under “Detecting T1055 Process Injection with Sysmon”; not verified execution.

  2. 02
    Decision

    When to Use

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

  3. 03
    Action

    Workflow

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

  4. 04
    Action

    Monitor CreateRemoteThread (Event 8): Detect when one process creates a thread in another process's address space. This is the primary indicator of classic DLL injection and shellcode injection.

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

  5. 05
    Action

    Analyze ProcessAccess (Event 10): Track cross-process handle requests with PROCESSVMWRITE (0x0020), PROCESSVMOPERATION (0x0008), and PROCESSCREATETHREAD (0x0002) access rights. Legitimate processes rarely need these on other processes.

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

  6. 06
    Action

    Detect Anomalous DLL Loading (Event 7): Identify DLLs loaded from unusual paths (user temp directories, download folders) into system processes.

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

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

    Hunt Process Hollowing (Event 25): Sysmon 13+ generates ProcessTampering events when the executable image in memory diverges from what was mapped from disk -- a hallmark of process hollowing (T1055.012).

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

  2. 08
    Action

    Correlate with Process Creation: Link injection events to the originating process creation (Event 1) to build the full attack chain from initial execution to injection.

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

  3. 09
    Action

    Filter Known-Good Cross-Process Activity: Exclude legitimate software that performs cross-process operations (debuggers, AV products, accessibility tools, RMM agents).

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

  4. 10
    Action

    Map to ATT&CK Sub-Techniques: Classify detected injection as classic injection (T1055.001), PE injection (T1055.002), thread execution hijacking (T1055.003), APC injection (T1055.004), thread local storage (T1055.005), process hollowing (T1055.012), or process doppelganging (T1055.013).

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

  5. 11
    Action

    Key Concepts

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

  6. 12
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  7. 13
    Action

    Detection Queries

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

  8. 14
    Action

    Splunk -- Suspicious ProcessAccess Patterns

    Source-described action candidate under “Splunk -- Suspicious ProcessAccess Patterns”; not verified execution.

  9. 15
    Action

    KQL -- Process Injection via Remote Thread

    Source-described action candidate under “KQL -- Process Injection via Remote Thread”; not verified execution.

  10. 16
    Action

    Sigma Rule -- Process Injection Detection

    Source-described action candidate under “Sigma Rule -- Process Injection Detection”; not verified execution.

  11. 17
    Action

    Common Scenarios

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

  12. 18
    Input

    Classic DLL Injection: Malware uses VirtualAllocEx + WriteProcessMemory + CreateRemoteThread to load a malicious DLL into a target process. Detected via Sysmon Event 8.

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

  13. 19
    Action

    Process Hollowing (RunPE): Attacker creates a suspended process, unmaps its image, writes malicious PE, and resumes execution. Detected via Sysmon Event 25.

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

  14. 20
    Action

    APC Injection: Malware queues an Asynchronous Procedure Call to threads of a target process using QueueUserAPC. Harder to detect, requires Event 10 monitoring.

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

  15. 21
    Action

    Reflective DLL Injection: DLL is loaded directly from memory without touching disk, bypassing ImageLoaded detection. Requires memory-level analysis.

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

  16. 22
    Action

    Process Doppelganging: Leverages NTFS transactions to replace a legitimate process image. Detected via process integrity checking.

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

  17. 23
    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

27 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

2 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 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

25 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 25 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/detecting-t1055-process-injection-with-sysmon/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/detecting-t1055-process-injection-with-sysmon/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/detecting-t1055-process-injection-with-sysmon
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.