Case 89DA50 · Cryptography · L4 Advanced

Malware Signed With Our Key

Practise as: Incident drillLevel: L4 Advanced

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.

  1. 01 What happened?
  2. 02 What is the impact?
  3. 03 What do you do?
What a strong answer covers

Try it out loud first. Then check yourself:

  1. Work out the path: key exported as a .pfx from a build or dev box, or the signing pipeline abused by someone with access.
  2. Impact: your reputation now vouches for malware; SmartScreen trust, EDR allowlists and customer app control rules let it run.
  3. Get the CA to revoke, choosing a revocation date before the first malicious signature; timestamped files signed after it fail.
  4. Re-sign legitimate releases with a new HSM-held key, notify customers and AV vendors, and share hashes of the malicious files.
  5. 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?

Go deeper

More Cryptography cards

All Cryptography cards →

cardosec draws a security topic and gives you a clock: explain it out loud with no notes, then see what you covered and what you missed. Free during early access.

Reviewed 2026-10-09