Products Lemma APIProof issuance & verification platformTrust402Delegate to agents, and transactSealSign-in for the agent era — no keys handed over
Use cases Manufacturing & Critical InfraInspection Record AssuranceFinance & FinTechCounterparty Record VerificationPublic SectorCertificate-less ProceduresHealthcareQualified Worker AssuranceProcurement & Supply ChainSupplier Credential MonitoringMedia & ContentContent AuthenticityService & RetailCross-group IdentityAI Adoption (cross-industry)AI Run GovernanceDevelopers & Agent OpsAgent Authority Control ▸ Browse the use-case index
Pricing
Resources Critical BriefThe frontier of AI × trustBlogThinking and implementation notesDocumentationAPI & specsVerification CenterReal verification & issuance countsAbout usFRAME00, Inc.ContactSales & press inquiriesGlossaryDefinitionsFAQFrequently asked questions
Dashboard ↗ JA
Home / Critical Brief / No. 178
No. 178 Critical Brief · Verifiable Origin

DigiCert: An attacker picked up EV code signing certificates for approved orders through the support portal (DigiCert incident report)

60
EV code signing certificates revoked; 27 of them were tied to the attacker (DigiCert report)
04-04→04-14
From the compromise of the second workstation to its discovery (DigiCert report)
04-17
The last certificate was revoked, with the revocation date set back to the date of issuance (DigiCert report)
CountryUS
Incident date2026-04-02
Published2026-11-05
AuthorsLemma Critical Team
Contents
  1. 01Summary
  2. 02What got through
  3. 03Pre-execution check
  4. 04What Lemma does
  5. 05Facts and timeline
  6. 06Sources

Summary

  1. 01What happened

    According to DigiCert’s report, the attacker got onto support analysts’ workstations and read, from the support portal, initialization codes for EV code signing orders that had been approved and were waiting for pickup. Certificates were issued in the names of genuine organisations, and some were used to sign malware.

  2. 02What was found

    Validation of the applying organisations went through the normal process, and the code plus an approved order was enough to obtain a certificate. Validation itself was not broken; what was intercepted was the final handover.

  3. 03Why it got through

    If holding a pickup code is enough to receive a certificate, the certificate can end up with someone other than the party that was validated, however sound the validation was.

Exhibit 1Detection vs pre-execution check

A pre-execution check means confirming, before a certificate is released, that the pickup request comes from a registered administrator of the validated subscriber, and keeping a record. Detection means noticing rogue certificates or the intrusion after issuance. Dates are from DigiCert's report (UTC).

Pre-execution check · not known from the disclosuresBefore release, match the pickup request to the subscriber's approval
What was confirmedCodes for approved orders were read
Certificates issued in genuine names
Detection · worked after issuanceResearchers' problem reports, scoping, revocation
04-02
A malicious file arrives through support chat
04-04
A second analyst's workstation is compromised
04-14
The second compromise is found; scope widens
04-17
The last certificate is revoked

What got through

What got through
Certificate pickup (key generation and issuance) against approved EV code signing orders. Using initialization codes read in the support portal, the attacker obtained certificates across several customer accounts and several issuing CAs (DigiCert report).
What reached the issuing side
In DigiCert’s report, pickup checks the initialization code and the approved order it belongs to. The code works for whoever holds it; whether the person picking up belongs to the validated organisation does not reach the CA. In general, the side running signed software also sees a valid signature issued in a genuine organisation’s name, and cannot tell it apart from the contents.
Not disclosed
Who the attacker is. Where the signed malware reached, and how many users. When the certificates were used (DigiCert says it does not track misuse dates). Why the second workstation had no endpoint sensor (DigiCert says the logs that would show this are past their retention period).

Pre-execution check

Whatever the route, the condition for telling them apart is that the pickup request is checked against a registered administrator of the validated subscriber, apart from the initialization code, before the certificate is released.

Pre-execution gate
Before releasing a certificate, check the pickup request with a registered administrator of the validated subscriber, not with the initialization code.
Who approves
A registered administrator of the validated subscriber. They confirm that the pickup request is theirs through a contact or device registered apart from the order and the code. Actions by the CA’s support staff, or by anyone merely holding the code, do not count as this approval.
Where it is checked
Before the certificate is generated against the approved order and delivered to a token. When a pickup request cannot be tied to the subscriber’s approval (for example, only the code was used), issuance is held.
What is recorded
Which order’s certificate went to which pickup request, with whose approval, so that you can later separate certificates that reached the subscriber from those that did not, and set the scope of revocation.

Detection did work: the first workstation was found and contained the next day, and certificates were revoked one by one as researchers reported them, but only after they had been issued and used to sign. Similar cases, where a trusted signature was accepted without checking where it came from, are xz utils (a maintainer who gained authority planted a backdoor in signed official releases) and SecondFi (external analysis says signing code was swapped for an unaudited SDK).

What Lemma does

Lemma builds the pre-execution check into the step where a CA releases the certificate for an approved order. It does not replace validation of the applicant or intrusion detection on endpoints; after them, it confirms before issuance that the pickup request is tied to the validated subscriber’s approval.

Industries and operations to watch

IndustryDevelopers & agent operations
Organisations that sign and ship their software with code signing certificates. Certificates can be issued in their name without ever reaching them.
IndustryProcurement & supply chain
Services that hand over certificates, keys or accounts by code or link after validation or contracting.
OperationSending & delivery
The final handover of something already validated or approved.
OperationAccounts & permissions
Features that let support staff view customer accounts from the customer’s perspective.

Current controls vs Lemma

The route in this case runs from the first column into the second. If the first does not stop it, the signatures in the second pass as valid signatures in a genuine organisation’s name. The third column is the response after issuance.

Control Pickup of certificates for approved orders Signing malware with the certificates Revocation after issuance
Validation of the applying organisation Not effective Not effective Not relevant
Endpoint monitoring of analysts (EDR) Partial Not relevant Not relevant
Researchers’ problem reports and revocation Not relevant Partial Effective
Lemma (pre-execution check) Effective Not effective Partial

Validation confirms that the applying organisation is genuine; here it was passed legitimately, and it does not check who picks up. Endpoint monitoring, per DigiCert’s report, found and contained the first compromise, but the second workstation had no sensor; it looks for intrusions, not at the pickup request itself. Researchers’ reports and revocation invalidated the certificates, but only after they had been used to sign. Lemma checks, before issuance, that the pickup request is tied to the validated subscriber’s approval. It does not stop signatures once a certificate is out, and it does not revoke certificates, but the record of which certificates went through the subscriber’s approval helps set the scope of revocation.

Note: Lemma’s check works only when it is built into the CA’s handover step and the subscriber’s registered administrators and contacts are managed apart from the support portal and order data. It passes if the subscriber’s administrator account itself is taken over. The same applies if the registered contact has been altered. The table compares what each control checks; it does not show whether this incident would have been stopped. Lemma does not detect or prevent intrusions, and it does not revoke certificates.

CheckChecklist

Three things to confirm for services that hand over certificates, keys or accounts

  • Are values that work for whoever holds them, such as pickup codes, kept off screens that support staff can view from the customer’s perspective?
  • For each pickup request, do you keep a traceable record of which certificate or key was released, with whose approval?
  • Do you have a step to reconcile certificates issued in your name against the certificates you actually received?

Facts and timeline

Party
DigiCert, a US certificate authority. Two support analysts’ workstations were compromised.
Entry point
Through the customer support chat, the attacker sent a file disguised as a customer screenshot. Four attempts were blocked; the fifth compromised the first workstation. The second was compromised through the same vector (DigiCert report).
What was taken
Initialization codes for EV code signing orders that were approved and awaiting pickup, read through a support portal function that lets analysts view customer accounts from the customer’s perspective. That function cannot manage accounts or orders, but the codes were not masked (DigiCert report).
Certificates
60 were revoked, from four CAs: two DigiCert CAs and CAs under the GoGetSSL and Verokey names. 27 were tied to the attacker (11 through problem reports from researchers and others, 16 through DigiCert’s investigation); the other 33 were revoked as a precaution because customer control could not be confirmed. Pending orders were cancelled (DigiCert report).
What was signed
The certificates identified by researchers had been used to sign the “Zhong Stealer” malware family (DigiCert report).
Contributing factors named by DigiCert
Inconsistent endpoint detection coverage; insufficient privilege minimisation in the support portal function; initialization codes not protected as bearer credentials; support channels accepting risky file types.
Other impact
DigiCert says it found no misuse of other internal systems or validation information, and no mis-issuance of non-code-signing certificates.

Glossary
EV code signing certificate — A certificate used to sign software and show which organisation made it. The certificate authority validates the applying organisation strictly before issuance; the key is kept on a hardware token.
Initialization code — The code entered to pick up the certificate for an approved order onto a token. In DigiCert's report, the code plus an approved order was enough to obtain the certificate.
Revocation — A certificate authority invalidating a certificate it issued, so that signatures made with it are no longer trusted.

Timeline

  • The attacker repeatedly sends malicious files to an analyst through support chat; one is opened on the first workstation.
  • Endpoint monitoring detects and contains the first workstation. At this point the second is not considered compromised.
  • A second analyst’s workstation is compromised through the same vector (established by the later investigation).
  • Certificate problem reports arrive from researchers and others; DigiCert revokes each within 24 hours.
  • The second compromise is found and the scope widens. Analyst accounts are suspended and a change masking initialization codes in the support portal is deployed in the US (API and EU the next day).
  • The last identified certificate is revoked, with the revocation date set to the date of issuance.
  • DigiCert files a preliminary report on Mozilla’s Bugzilla.
  • DigiCert posts its full incident report (revised on 05-04 and 05-05).
  • DigiCert reports all action items complete and requests closure.

The facts rely on DigiCert’s incident report on Mozilla’s Bugzilla and its later replies (primary). On the second workstation, DigiCert first described the sensor as malfunctioning, then revised this on 05-04 and 05-05 to say it was not installed. Help Net Security links Zhong Stealer to Chinese e-crime and cryptocurrency theft. It also reports that a researcher’s report helped uncover the second workstation. These are the outlet’s statements and are not in DigiCert’s report. What has not been disclosed does not mean there were no controls.

After disclosure

  • DigiCert: Masked initialization codes in both the support portal and the API, and made proxied support access read-only. Blocked risky file types in chat and case attachments and added sandboxing for attachments. Automated reconciliation of endpoint sensor enrolment and blocked non-compliant devices from corporate systems. Restricted initialization codes to authorised customer account administrators. It says all 21 action items are complete.
  • DigiCert’s commitments: To treat initialization codes as single-use bearer credentials throughout their lifecycle, including expiry. In its replies, DigiCert said the codes were valid for 30 days.
  • Industry discussion: In the Bugzilla thread, the chair of the CA/Browser Forum Code Signing Working Group noted that CAs cannot tell at issuance whether an organisation will later sign malware. DigiCert says it has seen an ongoing increase in social engineering attempts through its support channels in the same period.

Sources

  1. Primary, incident reportDigiCert “DigiCert: Misissued code signing certificates” (Mozilla Bugzilla 2033170, 2026-04-18 to 07-09)bugzilla.mozilla.org/show_bug.cgi
1 more (reporting, analysis)
  1. PressHelp Net Security “DigiCert breached via malicious screensaver file”2026-05-04 · helpnetsecurity.com/2026/…

References: “The last layer left in AI-era cyber defense”

The same method elsewhereSee all 21 "Account takeover" cases

This Brief sets out, from disclosed facts, what organisations in a similar position can check. It is not guidance on individual losses or procedures.

This material is a structured analysis of public information; it is not an audit, diagnosis, or recommendation for any specific organization.

Cite this Brief

Lemma Critical Team. (2026).
"DigiCert: An attacker picked up EV code signing certificates for approved orders through the support portal (DigiCert incident report)".
Lemma Critical Brief No.178. Lemma / FRAME00, Inc.
https://lemma.frame00.com/critical/briefs/178-digicert-ev-code-signing-issuance-hijack/
Read nextNext
All Briefs →
Lemma

If it can't be verified,
it doesn't enter your operation.

Lemma is a pre-execution check: logins, payments, records and publishing that look genuine are checked before they run, with cryptographic proofs the receiving side verifies without asking the issuer. Detection stays; the check sits in front of it.