CyberKit

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.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

Read next

Sources