durgabrgs.com

The Cyber Exposure Score is a published 0–100 formula built only from publicly observable signals. How this is calculated.

This domain scores better than 66% of the 473 Manufacturing organisations we track (cohort median 78). The sample is seeded from public incident data, not a random cross-section of the sector.

Posture summary

Software versions inside a published affected range (3, 3 known-exploited)

The public response carried a version for these products, and NVD publishes an affected range that contains it. This is not proof the software is unpatched — a distribution backport keeps the original version string while carrying the fix, so a fully patched build can appear here. Both halves of the comparison are public and checkable.

1 further match(es), with the affected range published for each, are part of the complete audit.

Ransomware leak-site listings (1)

This domain is named on the public leak site of a ransomware group. A leak-site post is a claim published by the group — not a verified fact, and not a statement by this organization. Groups list victims who did not pay, overstate what they hold, and occasionally name the wrong company. What is certain is that the listing itself is public.

Leak-site postings are collected here from 2026-07-30 onwards; an earlier listing would not appear above.

Source: Ransomware.live

Public attack surface (1 hostnames in Certificate Transparency)

Hostnames this organization published in public TLS certificates. Passive OSINT — nothing was scanned; a wildcard certificate is in use, so the real footprint may be larger.

The hostname inventory — which forgotten hosts exist and where — is part of the complete audit for this domain.

Recommendations

• criticalTreat data published on a leak site as disclosed

  This domain is named on Orova's public leak site on 2026-10-13. A leak-site post is a claim published by the group, not a verified fact — but the post itself is public, and if it is accurate the data is already out. Confirm the claim, then work from the assumption of disclosure: rotate every credential that touched the affected systems, invalidate active sessions, and check your notification duties under GDPR Art. 33/34.

• highCheck software versions that fall inside a published affected range (to be checked)

  The public response carried a version for 3 detected product(s), and 3 published CVE ranges contain what we read. PHP 8.1.34 falls inside the range published as affected by CVE-2026-109618 (>= 7.3.0 and < 8.2.35). 3 are on CISA's known-exploited list, meaning exploitation has been observed in the wild. This is an observation about a version string, not proof the software is unpatched: a distribution backport keeps the original version while carrying the fix. Check the build you are actually running, and patch or upgrade whatever is genuinely inside the range.

• mediumEnable DKIM

  No DKIM record was found on common selectors. Enable DKIM signing.

• mediumEnable DNSSEC

  DNSSEC signing was not detected for this domain.

• mediumUpgrade software past its end of life

  PHP 8.1: the project no longer fixes this release. A Linux distribution may still patch it, so check with whoever maintains the server, then plan the upgrade.

• lowUpdate JavaScript libraries with published issues

  jQuery 3.4.0: these versions have publicly listed issues. Whether they can be used against this site depends on how it calls them; updating is usually the quicker answer.