Incident
The D.R. Incident
incident:the_d_r_incident
Also: Dominican Republic incident
Episode-named incident involving a coordinated campaign against Dominican Republic government organizations, critical infrastructure, and a bank.
Explore relationships
Mentioned in
Relationships
Claims
The D.R. Incident
INVOLVES
Quantum ransomware
The Dominican Republic agricultural department suffered a ransomware attack attributed in the report to the Quantum ransomware group.
Explicit
Confidence 98%
· Host2
EP 135
Details
“The Dominican Republic’s agricultural department has suffered a ransomware attack by the Quantum ransomware group”
Host2 ·
offsets 9871–9984
The D.R. Incident
INITIAL_ACCESS_VIA
phishing
The investigation found that the attackers entered the network through a phishing attack.
Explicit
Confidence 99%
· Omar Avilez
EP 135
Details
“the attackers got into the network via a phishing attack”
Omar Avilez ·
offsets 11980–12036
The D.R. Incident
INVOLVES
Fortinet firewall vulnerability
The Quantum attackers exploited a Fortinet firewall vulnerability to obtain VPN access to the infrastructure.
Explicit
Confidence 98%
· Omar Avilez
EP 135
Details
“They exploited a vulnerability, a Fortinet firewall that allowed them to have VPN access to the infrastructure”
Omar Avilez ·
offsets 10700–10810
The D.R. Incident
INVOLVES
Bandook
Hundreds of phishing emails contained or used Bandook as the attackers' backdoor.
Explicit
Confidence 99%
· Jack Rhysider
EP 135
Details
“all of them had a backdoor the attackers were using, which was a backdoor known as Bandook”
Jack Rhysider ·
offsets 17780–17868
The D.R. Incident
INVOLVES
Cobalt Strike
A compromised system downloaded Cobalt Strike, and a later Cobalt Strike implant communicated with Conti's command-and-control infrastructure.
Explicit
Confidence 99%
· Jack Rhysider
EP 135
Details
“a system did get infected and it reached out to the command and control server to download Cobalt Strike”
Jack Rhysider ·
offsets 15514–15618
“they now downloaded or installed a second malware, which was a Cobalt Strike implant which was communicating to Conti’s C2”
Omar Avilez ·
offsets 22416–22538
The D.R. Incident
INVOLVES
Conti
The Dominican Republic campaign included Conti-related command-and-control activity and staged Conti ransomware, although the ransomware was stopped before execution.
Explicit
Confidence 97%
· Omar Avilez
EP 135
Details
“a Cobalt Strike implant which was communicating to Conti’s C2”
Omar Avilez ·
offsets 22477–22538
“they seemed to have stopped the Conti ransomware attack before it actually triggered ransomware on any systems”
Jack Rhysider ·
offsets 36742–36852
The D.R. Incident
ATTRIBUTED_TO
Russia
Omar says his partners told him Russia was involved in the Dominican Republic campaign, but he also presents the attribution as uncertain and based on what they learned during the investigation.
Uncertain
Confidence 72%
· Omar Avilez
EP 135
Details
“they told us that it was not just Dark Caracal; it was not just Conti, but also it was — Russia was also involved”
Omar Avilez ·
offsets 29510–29623
The D.R. Incident
ATTRIBUTED_TO
Dark Caracal
The campaign was associated with Dark Caracal in the investigation, but the episode emphasizes that attribution was not clear.
Uncertain
Confidence 72%
· Omar Avilez
EP 135
Details
“it was not just Dark Caracal; it was not just Conti”
Omar Avilez ·
offsets 29528–29579
“This attribution wasn’t exactly clear”
Jack Rhysider ·
offsets 33666–33703
The D.R. Incident
INVOLVES
operational technology
The campaign reached critical infrastructure, but the attackers could not disrupt the operational technology controlling it.
Explicit
Confidence 97%
· Omar Avilez
EP 135
Details
“They tried to but they could not. The critical infrastructure works — what we call the OT, which is operational technology”
Omar Avilez ·
offsets 37144–37266