Case 89DA50 · Cryptography · L4 Advanced
Malware Signed With Our Key
Live alertAt 10:15 threat intel flags a loader on VirusTotal carrying a valid Authenticode signature from your company release certificate; your signing HSM audit log has no request for that file hash.
- 01 What happened?
- 02 What is the impact?
- 03 What do you do?
What a strong answer covers
Try it out loud first. Then check yourself:
- Work out the path: key exported as a .pfx from a build or dev box, or the signing pipeline abused by someone with access.
- Impact: your reputation now vouches for malware; SmartScreen trust, EDR allowlists and customer app control rules let it run.
- Get the CA to revoke, choosing a revocation date before the first malicious signature; timestamped files signed after it fail.
- Re-sign legitimate releases with a new HSM-held key, notify customers and AV vendors, and share hashes of the malicious files.
- Fix root cause: non-exportable keys in HSM or cloud signing, approvals per signing request, and alerting on unusual signing.
If the interviewer pushes back
- Backdating revocation also invalidates genuine releases signed after that date. How do you choose the date and manage the fallout?