---
name: cyberstrikeus/T1070.010_relocate-malware
source: https://app.decimal.ai/s/cyberstrikeus-t1070-010-relocate-malware@1/SKILL.md
source_sha256: f45ba1bf5a2d
---

# T1070.010 Relocate Malware

> **Sub-technique of:** T1070

## High-Level Description

Once a payload is delivered, adversaries may reproduce copies of the same malware on the victim system to remove evidence of their presence and/or avoid defenses. Copying malware payloads to new locations may also be combined with File Deletion to cleanup older artifacts.

Relocating malware may be a part of many actions intended to evade defenses. For example, adversaries may copy and rename payloads to better blend into the local environment (i.e., Match Legitimate Resource Name or Location). Payloads may also be repositioned to target File/Path Exclusions as well as specific locations associated with establishing Persistence.

Relocating malicious payloads may also hinder defensive analysis, especially to separate these payloads from earlier events (such as User Execution and Phishing) that may have generated alerts or otherwise drawn attention from defenders. Moving payloads into target directories does not alter the Creation timestamp, thereby evading detection logic reliant on modifications to this artifact (i.e., Timestomp).

## Kill Chain Phase

- Defense Evasion (TA0005)

**Platforms:** Linux, macOS, Windows, Network Devices

## What to Check

- [ ] Identify if Relocate Malware technique is applicable to target environment
- [ ] Check Linux systems for indicators of Relocate Malware
- [ ] Check macOS systems for indicators of Relocate Malware
- [ ] Check Windows systems for indicators of Relocate Malware
- [ ] Assess detection coverage (1 detection strategies)

## How to Test

### Manual Testing

1. **Identify Attack Surface**: Determine if the target environment is susceptible to Relocate Malware by examining the target platforms (Linux, macOS, Windows).

2. **Assess Existing Defenses**: Review whether mitigations for T1070.010 are in place. If defenses are absent or misconfigured, this technique may be exploitable.

3. **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](https://github.com/redcanaryco/atomic-red-team) for updates.

## Remediation Guide

No specific mitigations documented for this technique.

## Detection

### Detection of Malware Relocation via Suspicious File Movement

## Risk Assessment

| Finding                               | Severity | Impact          |
| ------------------------------------- | -------- | --------------- |
| Relocate Malware technique applicable | High     | Defense Evasion |

## CWE Categories

| CWE ID  | Title                        |
| ------- | ---------------------------- |
| CWE-693 | Protection Mechanism Failure |

## References

- [Latrodectus APR 2024](https://www.proofpoint.com/us/blog/threat-insight/latrodectus-spider-bytes-ice)
- [DFIR Report Trickbot June 2023](https://thedfirreport.com/2023/06/12/a-truly-graceful-wipe-out/)
- [Atomic Red Team - T1070.010](https://github.com/redcanaryco/atomic-red-team/tree/master/atomics/T1070.010)
- [MITRE ATT&CK - T1070.010](https://attack.mitre.org/techniques/T1070/010)