TL;DR: Gunra ransomware combines Fortinet exploitation, NTDS credential dumping, pass-the-hash movement, and Shadow Copy deletion, while SafeBreach maps the campaign to ATT&CK simulations and CISA Alert AA26-222A guidance. The lesson is that perimeter compromise quickly turns into identity abuse unless privileged access, detection, and recovery controls are validated together.
At a glance
What this is: This is SafeBreach's analysis of Gunra ransomware coverage tied to CISA Alert AA26-222A, showing how edge exploitation, credential theft, lateral movement, and recovery suppression combine into a double-extortion path.
Why it matters: It matters because identity and privileged access controls are the real containment boundary once an attacker gets past the perimeter, and the article shows where those controls still fail in practice.
Context
Gunra is a ransomware-as-a-service operation that uses edge compromise as a starting point, then relies on credential abuse, lateral movement, and recovery disruption to make the intrusion profitable. In this kind of campaign, the security problem is not only initial access but the speed with which access turns into trusted internal movement.
For IAM and PAM teams, the relevant issue is that the attack chain depends on standing privilege, reusable credentials, and weak administrative segmentation. The article also shows a genuine NHI angle because service credentials, authentication bypasses, and reused sessions are part of the operational path from foothold to impact.
SafeBreach's coverage is a simulation-oriented read on a live threat advisory, so the practical question is whether controls detect the behaviours that matter after compromise. That makes the article more useful as a governance test than as a simple malware summary.
Key questions
Q: What breaks when edge access is allowed to become trusted internal identity use?
A: The control boundary breaks because a perimeter foothold can be converted into legitimate-looking authentication, administrative access, and lateral movement. In ransomware cases like Gunra, that means the attacker no longer needs to keep exploiting the edge once credentials, sessions, or privileged service paths are available. Identity assurance must therefore limit what a compromised gateway can do next.
Q: Why do dumped hashes and stolen sessions make ransomware harder to contain?
A: They let an attacker reuse existing trust instead of creating new malware or noisy exploits. A dumped hash or hijacked session can authenticate across systems, reach admin interfaces, and move laterally before defenders recognise the account has been abused. The result is faster spread, less visible activity, and a much shorter response window.
Q: What are the signs that pass-the-hash activity is underway in a network?
A: Look for unexpected SMB and RDP use between systems, privileged authentication from unusual hosts, and administrative access that does not match the user's normal behaviour. In a ransomware chain, these signals often appear after credential dumping and before encryption or data theft. Correlating them with edge incidents gives defenders earlier containment opportunities.
A: Security teams should assume recovery features will be targeted and build resilience before an incident begins. Protect backup systems, isolate administrative tooling, monitor for shadow copy deletion, and restrict who can run recovery-disrupting commands such as vssadmin and bcdedit. Offline or immutable backups matter because once the attacker removes local recovery points, restoration options shrink quickly and downtime becomes much harder to control.
Technical breakdown
How edge exploitation turns into trusted internal access
Gunra's initial access starts with exploitation of internet-facing appliances and weak authentication paths, which is typical of modern ransomware operations that prefer a perimeter weakness over noisy phishing. Once that foothold exists, the attacker does not need to remain at the edge. The real risk is that a trusted network service becomes the platform for account creation, remote service abuse, and repeated authentication attempts inside the environment. This is why edge security and identity governance cannot be treated as separate problems.
Practical implication: validate that firewall and VPN exposure does not create a durable internal trust path.
Why credential dumping and pass-the-hash remain effective
Credential dumping extracts reusable authentication material from a compromised system, while pass-the-hash lets an attacker authenticate without knowing the underlying password. In Gunra's case, NTDS dumping against domain controllers and subsequent pass-the-hash movement show how one credential event can cascade into broad privilege use. The control weakness is not only credential theft, but the existence of credentials that remain valid across too many systems and too long a window. That is a governance failure, not just a detection gap.
Practical implication: reduce credential reuse and limit where privileged hashes can authenticate.
How recovery inhibition amplifies ransomware impact
Gunra's operators pair encryption with recovery suppression, including Shadow Copy deletion and log clearing, so restoration becomes slower and more uncertain. This is not a separate stage from the attack, but part of the same control-breaking sequence: if backups, snapshots, and audit trails are removed, defenders lose both recovery options and evidence. The article's emphasis on behavior-based detection reflects a broader point: ransomware resilience depends on preserving restoration paths even after identity compromise has already occurred.
Practical implication: test that recovery controls survive privilege abuse, not just normal outage conditions.
Threat narrative
Attacker objective: The objective is to maximize ransom leverage by combining privileged internal movement, data theft, and recovery suppression before encryption completes.
- Entry begins with exploitation of internet-facing firewalls and VPN gateways, including authentication bypass and credential-access weaknesses that give the operators a foothold.
- Credential access follows through NTDS dumping, session theft, and pass-the-hash movement, allowing the actors to reuse trusted authentication material across the environment.
- Escalation and lateral movement continue through SMB, RDP, and administrative service abuse, which expands the compromise from one edge system into internal systems and domain assets.
- Impact comes from data exfiltration, Shadow Copy deletion, and file encryption, which together create double extortion pressure and degrade recovery options.
Breaches seen in the wild
- Cisco Active Directory credentials leak 2025: Kraken leaked Cisco Active Directory hashes, including service and krbtgt accounts; Cisco says they came from its 2022 breach, not a new one.
- Storm-2949 Azure Breach: Storm-2949 social engineering attack turns one cloud identity compromise into full Azure tenant breach.
Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.
NHI Mgmt Group analysis
Edge compromise is now an identity problem as much as a perimeter problem: Gunra shows that internet-facing exploitation only becomes decisive when it is paired with reusable credentials, privileged sessions, and weak internal trust boundaries. The campaign illustrates how quickly a gateway weakness becomes an identity governance failure once the attacker can impersonate internal users or services. Practitioners should treat exposed remote access systems as identity-control choke points, not standalone network assets.
Standing credential reuse remains the real lateral movement enabler: The article's NTDS dumping and pass-the-hash sequence is a reminder that attackers do not need a password once they can reuse a hash or session token. That is the practical failure mode, not merely credential theft in the abstract. This is where NHI governance and PAM intersect: service accounts, admin sessions, and cached authentication material can all become portable access objects if lifecycle and scope are weak. Practitioners should narrow the reuse window before an adversary does.
Recovery controls are part of identity resilience, not an afterthought: Gunra's Shadow Copy deletion and log clearing show that ransomware success depends on removing the evidence and restoration paths that limit blast radius. This is why detection, privilege restriction, and backup protection have to be validated together. The deeper lesson is that identity compromise is only contained when recovery channels remain available after administrative trust has been lost. Practitioners should test restoration paths under compromised-credential assumptions.
Attack simulation is the right validation model for campaigns like Gunra: SafeBreach's mapping to ATT&CK techniques underlines that control effectiveness should be tested against behaviours, not assumed from configuration. For identity programmes, that means measuring whether NTDS dumping, pass-the-hash, remote service abuse, and recovery inhibition are actually blocked or surfaced quickly. The named concept here is lateral movement validation gap: the mismatch between documented controls and whether those controls stop real post-compromise behaviour. Practitioners should close the gap with exercise-led verification.
What this signals
Lateral movement validation gap: Gunra shows why configuration compliance is not the same as attack resistance. Teams need proof that credential dumping, session reuse, and remote-service abuse are stopped in practice, not just controlled on paper.
The identity lesson extends beyond human users. Service accounts, administrative sessions, and cached authentication material can all become post-compromise transport mechanisms, so governance has to focus on where access can be reused and how quickly it can be revoked.
For practitioners
- Harden internet-facing access paths Prioritise patching and configuration review for VPN and firewall appliances that can expose administrative trust, especially where remote access leads into internal identity systems.
- Reduce credential portability Limit where privileged hashes, cached credentials, and reusable sessions can authenticate, and isolate domain controller access from routine administrative workflows.
- Protect recovery channels Back up and segment snapshots, Shadow Copy equivalents, and audit logs so a privileged attacker cannot erase both encryption recovery options and evidence in one move.
- Hunt for post-compromise identity abuse Alert on NTDS dumping, pass-the-hash movement, suspicious RDP and SMB use, and off-hours privileged activity that follows an initial edge event.
Key takeaways
- Gunra combines edge exploitation with credential abuse and recovery suppression, which makes identity governance part of ransomware containment rather than a separate discipline.
- The article's value is in the attack chain it maps, not just the alert it cites, because it shows how NTDS dumping and pass-the-hash convert initial access into enterprise movement.
- Controls that cannot withstand privileged credential reuse, remote service abuse, and Shadow Copy deletion are unlikely to hold once the attacker reaches the internal trust plane.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and MITRE ATT&CK address the attack and risk surface, while NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-02 — Secret Leakage | Gunra's NTDS dumping and session theft depend on exposed credentials and reused authentication material. |
| NHI-05 — Overprivileged NHI | The campaign turns reused access into lateral movement because too many identities can reach too many systems. | |
| Recommendation — Scan for exposed NHI and privileged credentials, then revoke any secret that can be reused after compromise. Reduce NHI privilege scope so a stolen identity cannot authenticate broadly across internal services. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Gunra's chain depends on weak credential lifecycle control and reusable authenticators. |
| Recommendation — Apply IA-5 to rotate and invalidate authenticators that could support post-compromise reuse. | ||
| MITRE ATT&CK | TA0006;TA0008 — Credential Access; Lateral Movement | The advisory centers on credential dumping followed by pass-the-hash and remote lateral movement. |
| Recommendation — Map detections to TA0006 and TA0008 to catch credential theft before it becomes enterprise spread. | ||
| CIS Controls v8 | CIS-5 — Account Management | The article highlights unrecognized accounts, reused credentials, and administrative abuse across systems. |
| Recommendation — Use CIS-5 to inventory and remove accounts that can be abused after an initial compromise. | ||
Key terms
- Pass-the-Hash: An authentication abuse technique where an attacker uses a stolen password hash instead of the cleartext password. It matters in Windows environments because cached credentials can sometimes be enough to gain access, turning one compromised host into a broader lateral movement opportunity.
- NTDS Credential Dumping: The extraction of Active Directory credential material from the NTDS.dit database, usually from a compromised domain controller. This is high-impact because it can expose many user and service account hashes at once, giving attackers reusable authentication material across the enterprise.
- Shadow Copy Deletion: The removal of Windows shadow copies, which are used as recovery points for files and system states. Attackers delete them to make restoration harder and to force victims toward backups that may be offline, incomplete, or also compromised.
- Lateral Movement: A post-compromise technique where an attacker uses a compromised NHI to move through a network, accessing additional systems and escalating impact without triggering detection.
Deepen your knowledge
NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, machine identity security, and secrets management for practitioners responsible for access control and lifecycle risk. It helps security teams connect identity governance to the broader controls that contain post-compromise abuse.
Published by the NHIMG editorial team on August 14, 2026.
Updated on October 12, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org