Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cyberstrikeus/T1027.005_indicator-removal-from-tools
Adversaries may remove indicators from tools if they believe their malicious tool was detected, quarantined, or otherwise curtailed.
Passed 16 of 23 test cases with the skill, and 11 of 23 without it.
and 2 more in the full report
5 fixed11 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
An adversary stopped the Endpoint Detection and Response service `sc stop Defender` and unloaded security driver filters on a Windows host. How is this activity classified under MITRE ATT&CK, and what is its technique ID?
| Checked | Without skill | With skill |
|---|---|---|
| Classifies disabling security services under T1562.001 Impair Defenses: Disable or Modify Tools. | Passed | Passed |
| Distinguishes disabling security tools from modifying malware artifacts to evade signatures. | Missed | Passed |
The instructions your model reads when the skill loads.
Sub-technique of: T1027
Adversaries may remove indicators from tools if they believe their malicious tool was detected, quarantined, or otherwise curtailed. They can modify the tool by removing the indicator and using the updated version that is no longer detected by the target's defensive systems or subsequent targets that may use similar systems.
A good example of this is when malware is detected with a file signature and quarantined by anti-virus software. An adversary who can determine that the malware was quarantined because of its file signature may modify the file to explicitly avoid that signature, and then re-use the malware.
Platforms: Linux, macOS, Windows
Identify Attack Surface: Determine if the target environment is susceptible to Indicator Removal from Tools by examining the target platforms (Linux, macOS, Windows).
Assess Existing Defenses: Review whether mitigations for T1027.005 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.
No specific mitigations documented for this technique.
test cases passed, vs 11 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.