HTML Smuggling
Reassembling a malicious file in the browser from script in an HTML page.
What it is
An evasion technique where the payload is encoded inside an HTML or script file and reconstructed locally by the browser (often via a data blob and an automatic download), so no malicious file traverses the network for inspection.
Why it matters
By building the file on the endpoint rather than transmitting it, smuggling slips past gateway and proxy scanning, making it a favored modern delivery method that pushes detection to the host.
In practice
Opening an attached HTML page that silently assembles and saves an archive containing a loader.
What to look for
- HTML attachments that build a file in the browser.
- Large base64 blobs inside script tags.
- Downloads that appear without a network request for the file.
Common mistake
Scanning only the network. The file is built on the endpoint, so watch the browser's downloads.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Email Header Analyzer
Walk the Received chain, and read the SPF, DKIM and DMARC verdicts.
- Phishing Case
A reported invoice email: pull the deciding values out of its raw headers, and say what they establish.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Microsoft Defender for Office 365 Commercial
Filters phishing and malicious attachments in Microsoft 365 and lets you investigate messages.
-
Proofpoint Email Protection Commercial
A mail gateway that scores, rewrites and quarantines suspicious mail.
-
VirusTotal Commercial
A quick second opinion on a suspicious attachment or link.
Read next
- Attachment-Based Delivery: Delivering malware as an email attachment the victim opens.
- Malicious Macro: Office document code that runs attacker logic when enabled.
- Quishing: Phishing that hides the malicious link inside a QR code.