SecureAEye LAB ONLINE · SIG 657 · DET ~41s

← All attacks / Social engineering and human-targeted attacks

HTML smuggling

HTML attachment assembles the payload locally with JavaScript, evading gateway inspection

categorySocial engineering and human-targeted attacksseverityVery Highdetectability (measured in our lab)Lowlabpartially detected

Example: NOBELIUM

Detection opportunity what to watch for

A benign emulation of this technique’s linchpin behaviour — the command an attacker runs, and where we’ve detonated it in the lab, exactly what the SIEM saw, what caught it, and what it missed.

What the attacker runs

ATT&CK T1027.006 · HTML Smuggling Remote Payload · Atomic Red Team
powershell -ExecutionPolicy Bypass -File C:\lab\detonate.ps1 -Technique T1027.006 -Tool atomic -RunId <run-id> -Command 'Invoke-AtomicTest T1027.006 -TestGuids 30cbeda4-08d9-42f1-8685-197fad677734 -GetPrereqs; Invoke-AtomicTest T1027.006 -TestGuids 30cbeda4-08d9-42f1-8685-197fad677734 -TimeoutSeconds 120'
ATT&CK T1027.006 · Atomic Red Team
powershell -ExecutionPolicy Bypass -File C:\lab\detonate.ps1 -Technique T1027.006 -Tool atomic -RunId run-2026-11-02-009 -Command 'Invoke-AtomicTest T1027.006 -TestGuids 30cbeda4-08d9-42f1-8685-197fad677734 -GetPrereqs; Invoke-AtomicTest T1027.006 -TestGuids 30cbeda4-08d9-42f1-8685-197fad677734 -TimeoutSeconds 120'

What our lab measured

partially detected windows · 2026-11-02 · detected in 44s

What it looked like in telemetry

Log sourceWhat it means
Sysmon · EID 1Powershell process spawned powershell instance
Sysmon · EID 10Session-token scraping: non-browser process opened browser memory with read access
Sysmon · EID 11Executable file dropped in folder commonly used by malware
Sysmon · EID 11Scripting file created under Windows Temp or User folder
PowerShell · EID 4104Powershell script querying system environment variables
PowerShell · EID 4104Powershell script recursively collected files from a filesystem search
PowerShell · EID 4104Powershell script searching filesystem
PowerShell · EID 4104Powershell script used "Invoke-command" cmdlet to execute sub script
… and 6 more event type(s)

Detection that fired

  • ✓ Wazuh 100202 (level 11) lab rule — Session-token scraping: non-browser process opened browser memory with read access

Plus 13 stock Wazuh/Sysmon rule(s) in the window.

Background noise in the window: ~11062 incidental alerts/hour — tune against this.

Classification

30 values: 9 reviewed, 2 lab-measured, 12 imported, 7 derived. What do these mean?

Exploitability

Attack vectorSocial engineering
Reach (CVSS)Local
Attack complexityLow
Privileges requiredNone
User interactionActive
Attacker skill requiredLow
Resources requiredLow
Likelihood / prevalenceHigh
MaturityCommoditized

Impact & scope

SeverityVery High
ImpactAvailabilityConfidentialityIntegrity
PlatformLinuxmacOSWindows
EnvironmentCloudOn-premises
Target asset classEndpoint
Kill-chain phase (tactic)Stealth

Detection & telemetry

Detectability (measured in our lab)Low
Detectability (public detection content)Low
Noise levelHigh
TestabilityAtomic Red Team test
Data sources (ATT&CK data components)File CreationNetwork Traffic ContentProcess Creation
Defense bypassedAnti-virusStatic file analysisWeb proxy

Detection & response

Mitigated by 1

Detected by 1

Tested by 1

  • 30cbeda4-08d9-42f1-8685-197fad677734 atomic

Lab findings

Measured in the isolated detection lab (Wazuh / Sysmon / auditd). Each run detonates a benign emulation of the technique and grades what the SIEM saw.

RunOutcomeToolPlatformRan at
run-2026-11-02-009partially-detectedatomicwindows2026-11-02
  • run-2026-11-02-009 — Backlog detectability-baseline probe (priority 7, 1 corpus attack(s); atomic_tests=1). No lab analytic covers this technique yet, so expected_wazuh_rules is empty and the grade is the true measured detectability: a bundled rule tagged T1027.006 firing is a real 'detected', nothing firing is a real coverage gap for the detection loop. Signals: bearing attack reads blind (detectability none/low); MITRE documents a detection strategy.; expected=0 incidental=295 max_level=15 dwell_s=90

Framework references

Evidence & sources

  • ev-0001 (Cyber Attack Taxonomy) — Name, definition and Example/ID taken verbatim from the 'Social engineering and human-targeted attacks' table, line 50 of Cyber-Attack-Taxonomy.md
  • ev-0002 (MITRE Enterprise ATT&CK v19.2 (STIX 2.1)) — ATT&CK usage prevalence: 3 groups/software/campaigns reference this technique (ATT&CK enterprise v19.2)
  • ev-0003 (Phase 4 detection lab - detonation runs 2026-11-02) — Lab detonation run-2026-11-02-009 (partially-detected) for T1027.006: no alert matched the expected technique