# Attack Ent T1059 006 Python > Analyze MITRE ATT&CK T1059.006 Python in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1059.006, Python, or enterprise ATT&CK. Adversaries may abuse Python commands and scripts for execution. - Skill: `santosomar/attack-ent-t1059-006-python` (Agent Skill, multi-file: 11 files) - Install (CLI): `npx skillmds@latest add santosomar/attack-ent-t1059-006-python` - Raw SKILL.md: https://api.skillmd.com/api/skills/santosomar/attack-ent-t1059-006-python/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - License: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See h - Author: santosomar (https://skillmd.com/u/santosomar) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/santosomar/attack-ent-t1059-006-python --- # MITRE ATT&CK T1059.006: Python ## When to use this skill Use this skill when the task involves T1059.006, Python, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK sub-technique. ## Technique context - ATT&CK domain: enterprise - ATT&CK ID: T1059.006 - Technique name: Python - Type: sub-technique - ATT&CK URL: https://attack.mitre.org/techniques/T1059/006 - Tactics: execution - Platforms: ESXi, Linux, macOS, Windows - Required permissions: Not specified - Effective permissions: Not specified - Defenses bypassed: Not specified ## ATT&CK description Adversaries may abuse Python commands and scripts for execution. Python is a very popular scripting/programming language, with capabilities to perform many functions. Python can be executed interactively from the command-line (via the python.exe interpreter) or via scripts (.py) that can be written and distributed to different systems. Python code can also be compiled into binary executables.(Citation: Zscaler APT31 Covid-19 October 2020) Python comes with many built-in packages to interact with the underlying system, such as file operations and device I/O. Adversaries can use these libraries to download and execute commands or other scripts as well as perform various malicious behaviors. ## Agent workflow 1. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning. 2. Load bundled resources as needed: use `references/technique-profile.json` for structured metadata, `references/detection-and-mitigation.md` for triage and telemetry guidance, `references/known-threat-context.md` for ATT&CK relationship context, and `templates/` for repeatable outputs. 3. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match. 4. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations. 5. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next. 6. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details. ## Bundled resources - `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique. - `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations. - `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions. - `templates/detection-brief.md`: detection engineering brief template. - `templates/hunt-plan.md`: threat hunt plan template. - `templates/incident-response-note.md`: incident response note template. - `templates/coverage-assessment.md`: ATT&CK coverage assessment template. - `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`. - `assets/output-schema.json`: JSON schema for structured technique analysis outputs. To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly. ## Detection guidance No ATT&CK detection guidance was present in the source STIX object. ## Useful telemetry and data sources - Not specified in the STIX object. ## Mitigations to consider - Antivirus/Antimalware - Audit - Execution Prevention - Limit Software Installation ## Known threat context Use these examples only as contextual leads, not as proof that an observed event is this technique: - APT29 (intrusion-set) - APT37 (intrusion-set) - APT39 (intrusion-set) - BRONZE BUTLER (intrusion-set) - Bandook (malware) - Bundlore (malware) - Chaes (malware) - Cinnamon Tempest (intrusion-set) - Cobalt Strike (malware) - CoinTicker (malware) - Contagious Interview (intrusion-set) - CookieMiner (malware) - Cutting Edge (campaign) - DRYHOOK (malware) - Donut (tool) - Dragonfly (intrusion-set) - DropBook (malware) - Earth Lusca (intrusion-set) - Ebury (malware) - FRAMESTING (malware) ## Recommended output pattern When responding with this skill, structure the answer as: - Assessment: whether the evidence supports this ATT&CK mapping and why. - Evidence: specific indicators, logs, behaviors, and assumptions. - Detection: telemetry sources, analytic logic, and tuning considerations. - Response: containment, eradication, recovery, and validation actions. - Coverage gaps: missing logs, sensors, controls, or environmental details. - References: include the ATT&CK URL and any user-provided evidence references.