Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for T1027.013.

Upgrade to Pro
T1027.013 Google Chronicle · YARA-L

Detect Encrypted/Encoded File in Google Chronicle

This detection identifies adversary use of encrypted or encoded files to conceal malicious payloads, configurations, or command-and-control artifacts from static analysis and signature-based detection. Adversaries commonly apply Base64 encoding, XOR ciphers, AES/RC4 encryption, or layered encoding schemes to files dropped on victim hosts, phishing attachments (password-protected documents, self-extracting archives), or scripts that decode and execute payloads at runtime. Detection focuses on processes decoding or decrypting file content, suspicious file entropy indicators surfaced via tooling, script interpreters reading encoded blobs, and the creation of high-entropy files in user-writable directories.

MITRE ATT&CK

Tactic
Defense Evasion
Technique
T1027 Obfuscated Files or Information
Sub-technique
T1027.013 Encrypted/Encoded File
Canonical reference
https://attack.mitre.org/techniques/T1027/013/

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule t1027_013_encoded_file_decode {
  meta:
    author = "argus-v1"
    description = "Detects processes decoding or decrypting encoded/encrypted file content, indicative of T1027.013 obfuscated payload staging."
    severity = "HIGH"
    tactic = "TA0005"
    technique = "T1027.013"

  events:
    $e.metadata.event_type = "PROCESS_LAUNCH"
    $e.target.process.file.full_path = /(?i)(certutil|powershell|pwsh|python|wscript|cscript|mshta)/
    (
      $e.target.process.command_line = /(?i)(-decode|-decodehex|-EncodedCommand|FromBase64String|openssl enc|base64 -d|\[Convert\]::FromBase64)/
    )
    $e.principal.hostname = $host

  condition:
    $e
}
high severity medium confidence

Chronicle YARA-L rule detecting process launch events where LOLBins or interpreter processes execute known file decoding or decryption argument patterns associated with obfuscated payload staging.

Data Sources

Chronicle SIEMGoogle WorkspaceWindows Event Logs via Chronicle

Required Tables

udm.events

False Positives & Tuning

  • Certificate management tooling using certutil decode in enterprise environments
  • PowerShell remoting infrastructure using encoded command serialization
  • Developer tools and automation scripts performing legitimate base64 decode operations

Other platforms for T1027.013


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1certutil Base64 Decode to Disk

    Expected signal: DeviceProcessEvents: certutil.exe with -decode argument; Sysmon Event ID 1 with CommandLine containing '-decode'; Sysmon Event ID 11 showing decoded_payload.bin creation in C:\Windows\Temp

  2. Test 2PowerShell In-Memory Base64 Payload Decode

    Expected signal: DeviceProcessEvents: powershell.exe with FromBase64String in command line; PowerShell Script Block Log Event ID 4104 containing FromBase64String and [Convert]::FromBase64; Sysmon Event ID 11 for decoded_ps_payload.bin creation

  3. Test 3OpenSSL AES Decrypt File on Linux

    Expected signal: Linux auditd execve syscall records for base64 and openssl processes; Syslog entries for process execution; Elastic Auditbeat process events showing openssl enc -d with -aes-256-cbc arguments; file creation event for decrypted_payload.bin in /tmp

Unlock playbooks & atomic tests with Pro

Get the full detection package for T1027.013 — response playbook and atomic red team tests, plus investigation guidance and hunting queries.

df00tech Pro — £29/user/month

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections