HTML smuggling

HTML smuggling is a delivery technique that uses browser features to reconstruct a file from encoded content in an HTML page or attachment, rather than transferring the finished file in its ordinary form.

The browser puts the file together

An HTML attachment or linked page can contain encoded data and script that turns it into a downloadable file. Attackers use ordinary browser features for this; the technique does not inherently require a browser vulnerability.

Reconstructing the file locally can make inspection harder for controls looking for a ready-made executable or archive crossing the network. It does not make the attack invisible to every email, browser, or endpoint control. Microsoft’s research describes both observed campaigns and ways to detect or block them.

Creating a file is not the same as running its contents

Browser script may run to assemble a file. Opening or executing the resulting payload is a separate event. In Microsoft’s documented Mekotio example, the page produced an archive and the later attack required further user actions.

That is different from ClickFix, where the lure asks the person to run supplied commands. Both can involve social engineering, but the step being requested is different.

If an unexpected attachment produces another file, stop and report it through your normal security channel. Do not open the new file to find out what it does. For the responder, preserve the connection between the original message, the generated file, and any later execution evidence.

The HTML attachment article includes a diagram of those stages and explains what each observation can establish.

Sources

See it in practice