Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cyberstrikeus/T1564.012_filepath-exclusions
Adversaries may attempt to hide their file-based artifacts by writing them to specific folders or file names excluded from antivirus (AV) scanning and other defensive capabilities.
Passed 18 of 21 test cases with the skill, and 14 of 21 without it.
and 5 more in the full report
4 fixed15 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
For our compliance mapping report on T1564.012, how many specific MITRE mitigations are defined for this sub-technique and what are their official M-identifiers?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies exactly two mitigations for T1564.012. | Missed | Passed |
| Lists M1049 and M1013 as the mitigations. | Missed | Passed |
The instructions your model reads when the skill loads.
Sub-technique of: T1564
Adversaries may attempt to hide their file-based artifacts by writing them to specific folders or file names excluded from antivirus (AV) scanning and other defensive capabilities. AV and other file-based scanners often include exclusions to optimize performance as well as ease installation and legitimate use of applications. These exclusions may be contextual (e.g., scans are only initiated in response to specific triggering events/alerts), but are also often hardcoded strings referencing specific folders and/or files assumed to be trusted and legitimate.
Adversaries may abuse these exclusions to hide their file-based artifacts. For example, rather than tampering with tool settings to add a new exclusion (i.e., Disable or Modify Tools), adversaries may drop their file-based payloads in default or otherwise well-known exclusions. Adversaries may also use Security Software Discovery and other Discovery/Reconnaissance activities to both discover and verify existing exclusions in a victim environment.
Platforms: Linux, macOS, Windows
Identify Attack Surface: Determine if the target environment is susceptible to File/Path Exclusions by examining the target platforms (Linux, macOS, Windows).
Assess Existing Defenses: Review whether mitigations for T1564.012 are in place. If defenses are absent or misconfigured, this technique may be exploitable.
Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.
Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.
test cases passed, vs 14 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.