In 30 seconds

DarkWebInformer reports that scans found copies of two distrusted certificate authorities in more than 100 Debian packages. The post warns that software relying on bundled certificates, rather than Debian’s central trust store, may still trust authorities the operating system removed.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
What happened
According to the post, Debian removed the emSign ECC Root CA G3 and Comodo AAA Services certificates from its trusted store on October 20, following an incident involving compromised eMudhra intermediate certificates. Subsequent scans allegedly located additional copies packaged with application files.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Why it matters
Removing a certificate from the operating system’s trust store may not affect applications that carry and consult their own certificate bundles. The report therefore suggests that Debian’s central revocation might not be applied consistently across every packaged application.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
What to do
The post says administrators are being urged to inspect application-specific certificate stores, including copies inside containers and virtual environments. It does not identify fixed package versions, so the evidence supports checking local certificate bundles rather than assuming that a particular upgrade resolves every instance.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Confirmed and still uncertain
The only supplied source names two certificates and says more than 100 packages contain copies. It does not provide the package list, scan output, methodology, affected versions, Debian advisory, remediation status, or evidence that every detected copy is active and trusted at runtime.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
What people are saying
DarkWebInformer says Debian developers discovered the remaining copies and explicitly cautions that not every package identified by the scan is necessarily vulnerable. No direct statement from Debian developers or maintainers is included in the supplied evidence.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Evolution
The sequence described by the source begins with compromised eMudhra intermediate certificates, continues with Debian removing two related authorities from its system trust store on October 20, and ends with scans allegedly finding bundled copies that remained in more than 100 packages.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Reach
1 independent groups, 1 updates, and 5 engagements.
Technical detail
The key distinction is between Debian’s shared certificate store and certificate files bundled inside individual packages. A copied certificate is not by itself proof of exposure: practical impact depends on whether an application loads that file, treats the certificate as trusted, and uses it during certificate validation.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Sources and evidence
The evidence batch contains one X post from DarkWebInformer and an attached HTTPS image. With no linked Debian notice, package inventory, scanner results, or maintainer confirmation, the package count, discovery attribution, and incident chain remain third-party claims rather than independently verified findings in this report.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Sources
- DarkWebInformerx.com · DarkWebInformer · x



