T1564.009 Resource Forking

sub-techniqueEnterprise

Adversaries may abuse resource forks to hide malicious code or executables to evade detection and bypass security applications. A resource fork provides applications a structured way to store resources such as thumbnail images, menu definitions, icons, dialog boxes, and code. Usage of a resource fork is identifiable when displaying a file’s extended attributes, using <code>ls -l@</code> or <code>xattr -l</code> commands. Resource forks have been deprecated and replaced with the application bundle structure. Non-localized resources are placed at the top level directory of an application bundle, while localized resources are placed in the <code>/Resources</code> folder. Adversaries can use resource forks to hide malicious data that may otherwise be stored directly in files. Adversaries can execute content with an attached resource fork, at a specified offset, that is moved to an executable location then invoked. Resource fork content may also be obfuscated/encrypted until execution.

01

platforms

Platforms this applies to.

macOS
02

tactics

ATT&CK tactics this technique serves.

03

sub-technique of

The broader entity this sits under.

04

mitigations

ATT&CK mitigations that reduce this.

05

detected by (3)

Data components that detect this.

06

countered by (D3FEND)

D3FEND countermeasures that counter this.

07

NIST CSF 2.0 — areas of relevance (Protect / Detect)

NIST CSF 2.0 areas this most relates to (evidence-ranked).

Derived from MITRE CTID (Apache-2.0) and the NIST 800-53 ↔ CSF crosswalk (public domain). Indicative relevance along the Protect/Detect axis — not a compliance assessment or coverage claim.

09

attack patterns (1)

CAPEC attack patterns that exploit this.

10

software (2)

Malware and tools associated with this.

11

source

Where this definition is published.