Trula Hacker Group Uses Custom Malware & Legacy Tools to Attack Government Organizations

https://gbhackers.com/trula-hacker-group-malware/

Accenture hazard scientists determined the group typical targeting European government organizations using their custom tools, albeit with some updates.

The group understands for carrying out different spear-phishing methods and watering-hole attacks to infect targeted victims. The group knows to be active given that at least 2014.

Trula, a sophisticated hacking group likewise known as Krypton, VenomousBear, Waterbug, Uroburos, or Snakegroup targets government entities, military, energy, and nuclear research study organizations.

Trula Group Attack

In the attack against European government organization, Trula used a mix of remote treatment call (RPC)- based backdoors, such as HyperStack, and remote administration trojans (RATs), such as Kazuar and Carbon.

The RPC backdoors are developed by Trula based on the relying RPC protocol, by using these backdoors they can carry out lateral motion and take control of other machines in the regional network without relying on the C&C server.

You can follow us on Linkedin, Twitter, Facebook for everyday Cybersecurity and hacking news updates.

Accenture Cyber Threat Intelligence scientists recognized that a person of the RPC backdoors used HyperStack functionality.

Earlier in May Turla Group Updated ComRAT Malware to Use Gmail web Interface for Command and Control.

Kazuar uses to link with the target C2 network that lives beyond the victim network, the C2 network is probably a compromised legitimate website.

Another version of HyperStack observed in this campaign that allows Trula operators to run a command via a named pipeline from the controller without implementing IPC$ enumeration activity.

For C&C interaction as like other cyber-espionage groups, Trula uses genuine web services. When it comes to the Carbon modular backdoor framework Pastebin utilized for C&C.

” HyperStack utilizes called pipes to carry out remote procedure calls (RPC) from the controller to the device hosting the HyperStack customer. To move laterally, the implant tries to connect to another remote devices IPC$ share, either utilizing a null session or default qualifications.”