T1070.010 Relocate Malware

Unter-TechnikEnterprise

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).

01

Plattformen

Plattformen, für die dies gilt.

LinuxmacOSNetwork DevicesWindows
02

Taktiken

ATT&CK-Taktiken, denen diese Technik dient.

03

Unter-Technik von

Die übergeordnete Entität.

05

NIST CSF 2.0 — Relevanzbereiche (Protect / Detect)

NIST-CSF-2.0-Bereiche mit dem größten Bezug (belegbasiert).

Abgeleitet aus MITRE CTID (Apache-2.0) und dem NIST-800-53-↔-CSF-Crosswalk (gemeinfrei). Eine indikative Relevanz entlang der Protect-/Detect-Achse — keine Compliance-Bewertung und keine Abdeckungsaussage.

06

Mindernde Maßnahmen (3)

Sicherheitskontrollen, die dies mindern.

07

Software (1)

Zugehörige Malware und Tools.

08

Quelle

Wo diese Definition veröffentlicht ist.