Masquerading
Also called Filename Spoofing.
Disguising malicious files or processes as legitimate ones.
What it is
Making attacker artifacts appear benign by mimicking the names, locations, icons, or metadata of legitimate software. A payload might be named like a system process or placed in a trusted directory to avoid scrutiny.
Why it matters
Masquerading exploits the human and tooling tendency to trust familiar names and paths, helping malware survive casual inspection. Verifying file paths, hashes, and signatures against known-good baselines is the practical countermeasure.
In practice
A binary named after a core Windows process is found running from a user's temp folder rather than the system directory, a classic giveaway.
What to look for
- System file names running from the wrong folder, such as svchost.exe outside System32.
- Names that are one character off, such as scvhost.exe.
- Files whose extension does not match their header, or double extensions.
Common mistake
Trusting the name or icon. Check the path, the parent process and the signature together.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Decoder
Paste any opaque value. It names what it looks like and why, then decodes it: Base64 and other layers, number bases, hashes, JWTs, certificates, SIDs, User-Agents and MAC addresses.
- Decode Range
Name an opaque value before you read it: timestamps, encodings and hashes, all generated by the site's own converters.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Atomic Red Team Open source
Small, scripted tests mapped to ATT&CK techniques, used to check whether a detection fires.
-
ATT&CK Navigator Open source
Lays techniques out on the ATT&CK matrix so teams can mark coverage, gaps and threat profiles.
-
Microsoft Defender for Endpoint Commercial
Tags its alerts with the ATT&CK techniques it observed on the host.
-
Sysmon Free
Supplies the host telemetry that most technique detections are written against. Our notes.
Read next
- Signed Binary Proxy Execution: Hiding code execution behind a trusted, signed system binary.
- Obfuscation: Deliberately making code hard to read or analyze.
- DLL Search-Order Hijacking: Planting a malicious library where a trusted program will load it.