Sophos analysts lately encountered a brand new EDR-killing utility being deployed by a legal group who have been attempting to assault a corporation with ransomware known as RansomHub. Whereas the ransomware assault in the end was unsuccessful, the postmortem evaluation of the assault revealed the existence of a brand new software designed to terminate endpoint safety software program. We’re calling this software EDRKillShifter.
Since 2022, we’ve seen a rise within the sophistication of malware designed to disable EDR methods on an contaminated system, as prospects more and more undertake EDR tooling to guard endpoints. Sophos beforehand revealed analysis about AuKill, an EDR killer software Sophos X-Ops found final yr that was being bought commercially inside legal marketplaces.
Through the incident in Could, the menace actors – we estimate with reasonable confidence that this software is being utilized by a number of attackers — tried to make use of EDRKillShifter to terminate Sophos safety on the focused laptop, however the software failed. They then tried to run the ransomware executable on the machine they managed, however that additionally failed when the endpoint agent’s CryptoGuard function was triggered.
How EDRKillShifter works
The EDRKillShifter software is a “loader” executable – a supply mechanism for a authentic driver that’s weak to abuse (also called a “carry your individual weak driver,” or BYOVD, software). Relying on the menace actor’s necessities, it could possibly ship quite a lot of completely different driver payloads.
There are three steps to the execution means of this loader. The attacker should execute EDRKillShifter with a command line that features a password string. When run with the right password, the executable decrypts an embedded useful resource named BIN and executes it in reminiscence.
The BIN code unpacks and executes the ultimate payload. This ultimate payload, written within the Go programming language, drops and exploits one in all quite a lot of completely different weak, authentic drivers to achieve privileges ample to unhook an EDR software’s safety.
Peeling off the primary layer
A superficial evaluation reveals that every one samples share the identical model knowledge. The unique filename is Loader.exe and its product identify is ARK-Recreation. (Some members of the analysis workforce speculated that the menace actor tries to masquerade the ultimate payload as a well-liked laptop sport named ARK: Survival Advanced.)
The binary’s language property is Russian, indicating that the malware writer compiled the executable on a pc with Russian localization settings.
All samples require a novel 64-character password handed to the command line. If the password is unsuitable (or not supplied), it gained’t execute.
When executed, EDRKillShifter masses an encrypted useful resource named BIN, embedded inside itself, into reminiscence. It additionally copies that knowledge into a brand new file named Config.ini and writes that file to the identical filesystem location the place the binary was executed.
The loader code then allocates a brand new reminiscence web page utilizing VirtualAlloc, and writes the encrypted content material into the newly allotted web page. The malware then deletes the config.ini file and proceeds with decrypting the subsequent set of payloads – the abusable driver and a Go binary. The loader makes use of a SHA256 hash of the enter password because the decryption key of the second-layer payloads.
If the malware efficiently decrypts the second-layer payloads, it creates a brand new thread and begins execution in that thread.
Loading the ultimate EDR killer into reminiscence
The second stage is obfuscated via the usage of a self-modifying code method. Throughout runtime, the second layer alters its personal directions. Because the precise executed directions are solely revealed throughout execution, further tooling or emulation is required for evaluation.
The determine beneath additional illustrates the method. The primary part reveals the start of the self-modifying code layer. All directions after the primary name within the disassembly are nonsense at this level. If we revisit the identical instruction block after executing the primary name, we see a distinct set of directions. The primary name modifies the subsequent set of directions, which then modifies the subsequent set of directions, and so forth.
The only goal of the ultimate, decoded layer is to load the ultimate payload dynamically into reminiscence and execute it.
Evaluation of the last word payload
The entire samples we analyzed executed a distinct EDR killer variant in reminiscence. They’re all written in Go and obfuscated (probably via the usage of an open-source software named gobfuscate). Obfuscators are instruments designed to hinder reverse engineering. There could also be authentic causes for software program engineers to obscure the software program, similar to to stop opponents from stealing mental property. Nonetheless, malware authors additionally use obfuscators to make it harder for safety researchers to investigate malware.
Most reverse engineers depend on this obfuscated knowledge when analyzing malware written in Go, however on this case, this key knowledge is obscured within the compiled code. A few of this info consists of:
- Strings are encrypted. They are going to be decrypted throughout runtime.
- The Go model info is gone. A variety of open-source reverse engineering instruments depend on this Go model info to rebuild constructions within the disassembly.
- Helpful bundle info, or bundle paths, are encrypted or stripped from the ultimate malware.
Nonetheless, we have been in a position to extract precious info utilizing the GoReSym software from Mandiant.
Similarities between the ultimate payloads
The entire unpacked EDR killers embed a weak driver within the .knowledge part. Their habits is simple, like different EDR killers we’ve got analyzed[1][2][3]. The one main distinction between the 2 variants we checked out is the weak driver being loaded and exploited.
Upon execution, each variants purchase the required privileges to load a driver and drop the exploitable sys file into the AppDataLocalTemp folder. The malware generates a random filename for the motive force each time it’s run.
After the malware creates a brand new service for the motive force, begins the service, and masses the motive force, it enters an infinite loop that constantly enumerates the operating processes, terminating processes if their identify seems in a hardcoded listing of targets. This habits is constant for each variants.
It’s also price noting that each variants exploit authentic (although weak) drivers, utilizing proof-of-concept exploits obtainable on Github. We suspect that the menace actors copied parts of those proofs-of-concept, modified them, and ported the code to the Go language. It is a widespread development we’ve got additionally noticed in different EDR killers, similar to Terminator.
Identical loader, completely different ultimate payloads
The pattern with SHA256 451f5aa55eb207e73c5ca53d249b95911d3fad6fe32eee78c58947761336cc60 abuses a weak driver that has additionally been seen abused in assaults and calls itself RentDrv2. A proof-of-concept for exploiting this driver is obtainable on Github.
The variant may also obtain a further command line argument “–listing”, permitting adversaries to move a further listing of course of names as targets.
The variant with SHA256 d0f9eae1776a98c77a6c6d66a3fd32cee7ee6148a7276bc899c1a1376865d9b0 in distinction, abuses a known-vulnerable driver known as ThreatFireMonitor, a part of a deprecated system-monitoring bundle. A proof of idea for this particular driver can also be obtainable on Github.
Mapping EDRKillShifter into the bigger menace panorama
The ultimate payload embedded into the loader modifications from incident to incident (and, presumably, creator to creator). If we attempt to map EDRKillShifter to the bigger menace panorama, it’s also believable that the loader and the ultimate payloads are developed by separate menace actors.
Promoting loaders or obfuscators is a profitable enterprise on the darkish internet. Sophos X-Ops suspects that the loader’s sole goal is to deploy the ultimate BYOVD payload, and that it may need been acquired on the darkish internet. The ultimate EDR killer payloads are then merely being delivered by the loader itself, which consists of the layer 1 and a pair of we described in our evaluation above.
It’s worthwhile to notice that we’re unable to substantiate this speculation at the moment.
Mitigations and recommendation
Sophos presently detects EDRKillShifter as Troj/KillAV-KG. Moreover, behavioral safety guidelines that shield towards protection evasion and privilege escalation block these system calls from going via. Companies and particular person folks may also take further steps to defend their machines towards driver abuse:
- Sophos X-Ops strongly suggests that you just examine whether or not your endpoint safety product implements and allows tamper safety. This function offers a robust layer towards such kind of assaults. In case you use Sophos merchandise however don’t presently have Sophos tamper safety enabled, flip it on in the present day.
- Observe sturdy hygiene for Home windows safety roles. This assault is barely potential if the attacker escalates privileges they management, or if they will receive administrator rights. Separation between person and admin privileges may also help stop attackers from simply loading drivers.
- Hold your system up to date. Since final yr, Microsoft has begun to push updates that de-certify signed drivers recognized to have been abused previously.
