EgregorMalware
According to Heimdal, Egregor ransomware infection happens via a loader, then, in the victim’s firewall, it enables the Remote Desktop Protocol. After this part, the malware is free to move inside the victim’s network, identifying and disabling all the antivirus software it can find.From MISP Galaxy
Last reported 5 years ago, by Group-IB4 reports
ATT&CK techniques
6 of 9 · each with the sentence it comes from- T1021.001Remote Desktop Protocol
“It was used by the threat actors to modify registry and firewall rules to enable connections via Remote Desktop Protocol.”
- T1110Brute Force
“Failed user login event (brute-force)”
- T1036Masquerading
“In addition, they used Rclone for data exfiltration – the same masquerading technique was used, they renamed its binary to svchost.exe and placed it to C:Windows.”
- T1053.005Scheduled Task
“Usually the threat actors try to deploy ransomware as widely as possible, and use PsExec or Group Policy modification to run a scheduled task to run it.”
- T1110.001Password Guessing
“failed user login – credential access (password guessing) user creation event – persistence”
- T1110.003Password Spraying
“It’s important to note that the RaaS affiliates rarely perform brute force or password spraying attacks against such instances themselves, rather they buy accesses from the brokers.”
What the reports say
4 reports, newest first · the exact sentence from each-
REvil Twins: Ransomware-as-a-Service program“In the past, IcedID was known to have been used by Maze, Egregor and Conti affiliates, while Qakbot – by ProLock, Egregor and DoppelPaymer.”
-
Connecting the Bots“Similar scripts were observed to be used by ProLock and Egregor operators.”
-
The source of everything“…uration, Microsoft 10 source code and builds were leaked, and Watch Dogs: Legion source code ended up online after Ubisoft was hit with Egregor ransomware.”
-
The Locking Egregor“The Locking Egregor”
Indicators in its reports
named in the reports above- exploit[.]inin 1 report
- hxxp://gitlab.test[.]net/in 1 report
- gitlab.test[.]netin 1 report
- hxxp://gitlab.test[.]net/admin/users/ferdinandin 1 report
- hxxp://gitlab.test[.]net/-/profile/personal_access_tokensin 1 report
- hxxp://jenkins.test[.]net:8080/in 1 report
- jenkins.test[.]netin 1 report
- hxxp://jenkins.test[.]net:8080/login?from=%2Fin 1 report
- hxxp://jenkins.test[.]net:8080/loginErrorin 1 report
- hxxp://jenkins.test[.]net:8080/managein 1 report
- hxxp://jenkins.test[.]net:8080/securityRealm/in 1 report
- hxxp://jenkins.test[.]net:8080/securityRealm/addUserin 1 report
- hxxp://jenkins.test[.]net:8080/job/secure-service/in 1 report
- hxxp://gitlab.test[.]net/root/secure-servicein 1 report
- hxxp://jenkins.test[.]net:8080/job/secure-service/12/ws/in 1 report
- hxxp://jenkins.test[.]net:8080/job/secure-service/12/execution/node/3/ws/in 1 report
Copy these 16 indicators · defanged
Thanks — we review every report.