Hinduja Tech compromised, BMW and Škoda credentials leaked

26 July 2026 elevated threat manufacturingtransportationtechnology

Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.

Ransomware gang claims breach of Hinduja Tech with 187 compromised user accounts and 73 third-party employee credentials exposed.

A ransomware operator has publicly claimed a breach of Hinduja Tech affecting systems and credentials associated with BMW Group and Škoda Auto. The disclosure indicates 187 compromised user accounts and 73 third-party employee credentials were exfiltrated. The leak includes DNS records and screenshots of accessed systems, indicating reconnaissance and credential theft. The breach appears to have been leveraged for extortion, with the ransomware gang publicly posting victim details on their leak site. Defenders at affected organizations should assume compromised credentials are in attacker hands and assess exposure to lateral movement, persistence, and further intrusion.

Mentioned in this report

Threat actors Global Secret Group

Detection guidance

Entra ID Identity Protection Leaked Credentials Detection

ATT&CK T1078.004

Identity Protection flagged a user as having credentials found in a leak or dump, which is the exposure the Hinduja Tech disclosure implies for third-party employee accounts. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.

title: Entra ID Identity Protection Leaked Credentials Detection
id: 0932b900-2f6f-5568-a4fe-7cd14c1975e8
status: experimental
description: Detects an Entra ID Identity Protection risk detection of type leakedCredentials.
  This means a user's valid cloud credentials were found in a public leak or dump,
  as claimed in the Hinduja Tech extortion disclosure. Treat the account as attacker-held
  and review its sign-ins for use of valid cloud accounts.
tags:
- attack.initial-access
- attack.persistence
- attack.stealth
- attack.t1078.004
logsource:
  product: azure
  service: riskdetection
detection:
  selection:
    riskEventType: leakedCredentials
  filter_remediated:
    riskState:
    - remediated
    - dismissed
    - confirmedSafe
  condition: selection and not filter_remediated
falsepositives:
- Users whose credentials leaked from an unrelated personal-service breach and who
  reuse the password on the corporate account
- Test accounts deliberately seeded in credential-leak monitoring exercises
level: high
author: Vorant
references:
- https://www.ransomware.live/id/SGluZHVqYSBUZWNoIHwgQk1XIEdyb3VwICYgxaBrb2RhIEF1dG9AR2xvYmFsIFNlY3JldCBHcm91cA==

Successful Entra ID Sign-in With High Sign-in Risk

ATT&CK T1078.004

A successful cloud sign-in that Identity Protection scored as high risk, consistent with leaked or stolen credentials being used. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.

title: Successful Entra ID Sign-in With High Sign-in Risk
id: b642cc12-1560-541a-bb77-defa4915ae95
status: experimental
description: Detects successful Entra ID sign-ins where Identity Protection assessed
  the sign-in risk as high. This can indicate attackers using stolen or leaked credentials,
  as in the Hinduja Tech and BMW/Skoda credential leak. Requires Entra ID P2 risk
  signals in the sign-in logs.
tags:
- attack.initial-access
- attack.persistence
- attack.t1078.004
logsource:
  product: azure
  service: signinlogs
detection:
  selection:
    ResultType: 0
    RiskLevelDuringSignIn: high
  condition: selection
falsepositives:
- Legitimate users travelling or using anonymizing VPNs, which can raise sign-in risk
- Users signing in from newly provisioned devices or locations before risk is remediated
level: medium
author: Vorant
references:
- https://www.ransomware.live/id/SGluZHVqYSBUZWNoIHwgQk1XIEdyb3VwICYgxaBrb2RhIEF1dG9AR2xvYmFsIFNlY3JldCBHcm91cA==

Behavioural rules are generated from public reporting — validate in your environment before deploying.

Source reporting: https://www.ransomware.live/id/SGluZHVqYSBUZWNoIHwgQk1XIEdyb3VwICYgxaBrb2RhIEF1dG9AR2xvYmFsIFNlY3JldCBHcm91cA==

What this brief leaves out

This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.

It sits in a corpus of 13,854 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.

A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.

Create a free account What it costs