- Home
- Techniques
- Enterprise
- Masquerading
- Invalid Code Signature
Masquerading: Invalid Code Signature
Other sub-techniques of Masquerading (6)
| ID | Name |
|---|---|
| T1036.001 | Invalid Code Signature |
| T1036.002 | Right-to-Left Override |
| T1036.003 | Rename System Utilities |
| T1036.004 | Masquerade Task or Service |
| T1036.005 | Match Legitimate Name or Location |
| T1036.006 | Space after Filename |
Adversaries may attempt to mimic features of valid code signatures to increase the chance of deceiving a user, analyst, or tool. Code signing provides a level of authenticity on a binary from the developer and a guarantee that the binary has not been tampered with. Adversaries can copy the metadata and signature information from a signed program, then use it as a template for an unsigned program. Files with invalid code signatures will fail digital signature validation checks, but they may appear more legitimate to users and security tools may improperly handle these files.[1]
Unlike Code Signing, this activity will not result in a valid signature.
Procedure Examples
| Name | Description |
|---|---|
| Regin |
Regin stage 1 modules for 64-bit systems have been found to be signed with fake certificates masquerading as originating from Microsoft Corporation and Broadcom Corporation.[2] |
| Windshift |
Windshift has used revoked certificates to sign malware.[3][4] |
| WindTail |
WindTail has been incompletely signed with revoked certificates.[3] |
Mitigations
| Mitigation | Description |
|---|---|
| Code Signing |
Require signed binaries. |
Detection
Collect and analyze signing certificate metadata and check signature validity on software that executes within the environment, look for invalid signatures as well as unusual certificate characteristics and outliers.