The Trust Factory Was Compromised: How Zhong Stealer Stole 27 Code-Signing Certificates From DigiCert
TL;DR
In April 2026, threat actors from the Zhong Stealer group compromised two DigiCert employee PCs and gained unauthorized access to the company's certificate issuance portal. They stole 27 code-signing certificates, used them to sign malware and bypass Windows SmartScreen, then distributed the signed payloads to targets. Affected customers span 13 countries including Lenovo, Shuttle, Tencent (TikTok operator), and others. This is a keystone-moment supply-chain attack: when a certificate authority itself becomes the attack vector, every downstream organization using those certificates is exposed.
What Happened
On April 3, 2026, DigiCert's Trust Operations team detected the initial compromise on two customer service employee computers. By April 4, they found the second system had been silently compromised via the same delivery vector—but the damage was already done.
The attackers (attributed to Zhong Stealer, a group known for targeting customer-service representatives) had already stolen 27 legitimate code-signing certificates from DigiCert's protected customer portal and used them to sign malware, allowing the payloads to pass Windows SmartScreen filters and deploy to end-user machines with apparent legitimacy.
DigiCert's post-incident investigation uncovered 33 additional suspicious certificates and immediately revoked all 60 within 24 hours of discovery.
The Kill Chain
1. Initial compromise: Attackers infected DigiCert customer service employee PCs with malware
2. Portal access: Criminals gained unauthorized access to DigiCert's customer portal (which had a function simulating customer access)
3. Certificate theft: Attackers retrieved initialization codes stored in the portal, combined with physical hardware tokens from customers, to obtain private key material and certificates
4. Signing + distribution: Used the hijacked certificates to sign malware, allowing Windows SmartScreen to verify the signatures as "trusted"
5. Downstream impact: Malware signed with stolen DigiCert certificates deployed to hundreds or thousands of end-user machines
Affected Customers & Geographic Scope
DigiCert's disclosed customer list includes:
- PC manufacturers: Lenovo, Shuttle, Palit
- Major tech: Tencent (TikTok operator)
- Security vendors: DigiFors (Leipzig)
- Geographic footprint: 61 certificates from 13 countries, with heavy concentration in Asia but also EU companies affected (Germany, Switzerland, France, Poland, Portugal)
Technical Details
The Authentication Bypass Chain
The attack exploited three critical gaps in DigiCert's security posture:
1. Endpoint detection failure: One of the two compromised computers did not have a CrowdStrike sensor installed. The attackers dwell inside that system for 10 days undetected. The second system did have an alarm trigger but the malware executed before containment.
2. Portal security gap: DigiCert's Salesforce-based customer portal forwarded suspicious files (a .scr file in ZIP format) directly to support staff without content filtering or sandboxing, providing ideal initial access.
3. Certificate initialization design flaw: The system stored certificate initialization codes in the portal without adequate access controls, and didn't require out-of-band authorization for certificate retrieval when combined with a customer's physical hardware token.
Windows SmartScreen Bypass
The hijacked certificates allowed attackers to sign PE binaries (executables) with legitimate DigiCert code-signing credentials. When users download and execute these files:
- Windows SmartScreen validation checks the certificate signature
- The signature is valid (issued by DigiCert, a trusted CA)
- The file is not flagged as unknown
- Execution proceeds without user friction
This effectively erases one of the last behavioral signals that security vendors rely on to detect malware distribution.
Scope of Malware Deployment
DigiCert has not disclosed the total number of compromised systems across all affected customers. However, given that Lenovo and Shuttle are in the list, and these are OEMs shipping to millions of devices, the downstream impact could affect hundreds of thousands or more machines—many of which may not yet know they were targeted.
Lyrie Assessment: Why CISOs Must Act Now
This attack violates three foundational assumptions of enterprise security:
1. **Certificate Authorities Are Supposed to Be Unhackable**
You trust DigiCert because they're supposed to be at the top of the PKI pyramid. If an attacker can steal certificates from a CA, they can:
- Impersonate any domain you own (if they steal your TLS certificate)
- Sign malware that passes all certificate validation
- Redirect traffic to phishing infrastructure with valid HTTPS
- Deploy ransomware that looks digitally legitimate to endpoint protection tools
DigiCert's breach proves this assumption is dead.
2. **Third-Party Trust Is Now an Attack Multiplier**
Every organization in that customer list is now in breach response mode:
- Are there signed malware samples using my certificate in the wild?
- Did my customers download and execute them?
- How many endpoints are running malware signed with my certificate?
- Do I need to revoke my own code-signing certificates?
Lenovo, Shuttle, and Palit will spend weeks tracing the blast radius. Their customers (millions of end-users and enterprises) won't know they were targeted until incident response teams report back.
For Lyrie's audience: This is the supply-chain attack that breaks defense-in-depth. No amount of endpoint isolation, network segmentation, or SOC detection rules matter if malware arrives with a valid certificate from a trusted CA.
3. **Endpoint Detection Gaps Are Still the Weak Link**
One of the two compromised DigiCert systems was not running CrowdStrike Falcon—the other major EDR platform. That's how the attackers dwell inside for 10 days undetected.
This repeats a pattern from 2025: the most consequential breaches happen in organizations that:
- Have gaps in EDR coverage (offline systems, legacy networks, customer-service terminals)
- Assume third-party tools will catch everything
- Don't enforce hardware-backed identity controls
4. **The Real Window Is Asymmetric**
DigiCert detected and contained the first compromise in hours on April 3. The second system compromised April 4. By April 5-30 (the month it took for public disclosure), the attackers had already:
- Weaponized 27 certificates
- Signed malware payloads
- Distributed them to customers
- Possibly owned downstream endpoints
By the time CISOs learned about this on May 4-5, the incident was 4 weeks old. Defenders were playing catch-up on an attack that had a month head start.
Recommended Actions
Immediate (Next 24 Hours)
1. Check if your organization was in the affected customer list (DigiCert published partial list; check your vendor relationships)
2. Audit your code-signing certificate inventory — Do you have a certificate issued by DigiCert between April 1-10? If so, assume it may be compromised
3. Revoke and re-issue code-signing certificates — If your company received DigiCert certificates during this window, revoke and reissue immediately, even if no breach evidence exists
4. Check Microsoft Sentinel/Windows Defender for detections of "Trojan:Win32/Cerdigent.A!dha" or executables signed by stolen DigiCert certificates
Short-Term (This Week)
1. Endpoint audit: Query all endpoints for files signed by:
- DigiCert certificates issued between April 1-10, 2026
- Files signed with certificate serial numbers matching the public revocation list
2. Supply-chain investigation: Contact your vendors (Lenovo, Shuttle, if applicable) and ask directly if they distributed signed malware
3. Establish certificate pinning: For critical infrastructure, implement HTTPS certificate pinning to reduce reliance on CAs
4. EDR coverage audit: Verify 100% of endpoints (especially customer service, support, and admin systems) have real-time EDR monitoring. Fill any gaps immediately
Medium-Term (This Month)
1. Code-signing process hardening:
- Move code-signing keys to hardware tokens (not stored on disk)
- Require multi-party approval for certificate retrieval
- Enforce out-of-band authorization (SMS/TOTP) for certificate use
- Log and alert on all certificate retrieval events
2. Zero-trust supply chain: If your dependencies (libraries, OS images, container base images) ship signed binaries, verify the signature chain and the CA issuer. Don't assume a valid signature means safe code.
3. Threat hunting: Search for files signed with certificates from the DigiCert revocation list across your entire environment (cloud, on-prem, endpoints, supply-chain systems). Assume any matches are malicious until proven otherwise.
Sources
1. DigiCert Official Statement - Microsoft Defender Incorrectly Flagged DigiCert Root Certificates
2. Heise Online - After Malware Attack: Criminals Used DigiCert's Code-Signing Certificates
Lyrie.ai Cyber Research Division
Lyrie Verdict
Lyrie's autonomous defense layer flags this class of exposure the moment it surfaces — no signature update required.