Security researchers discovered that the Trickbot Trojan has replaced its “mworm” propagation method with a new “nworm” module.

In April 2020, Palo Alto Networks’ Unit 42 observed Trickbot deploy its new propagation method during an attack on a laboratory environment in which the malware produced nworm on an infected Windows 7 client. Via the use of a Server Message Block (SMB) exploit, the method helped Trickbot move to a Windows domain controller (DC).

Trickbot’s newest module replaced mworm, a propagation capability that the malware first began using in September 2019. Like mworm, its latest feature didn’t appear unless the malware infection occurred in an Active Directory (AD) environment with a DC. When it did infect a vulnerable DC via nworm, however, the malware ran from memory and left no artifacts as a means of evading detection. Additionally, Trickbot didn’t survive a reboot of the infected DC. Unit 42 noted that this property didn’t pose an issue for the malware, given the fact that DCs and servers don’t shut down as frequently as Windows clients.

A Look Back at Trickbot’s Recent Attacks

Back in January, SentinelOne observed the malware enterprise leveraging its PowerTrick backdoor as a means of preying upon high-value targets. In March, Fortinet detected a new variant of the malware being distributed by a Microsoft Word document. A month later in April, Zscaler detected that Trickbot’s handlers had made several changes to their creation, including the addition of several Italian banks to Trickbot’s list of targets.

Defend Against Trickbot’s Nworm Module

Security professionals can help defend against nworm and Trickbot’s other propagation modules by using security information and event management (SIEM) data to learn about the context of relevant software vulnerabilities. They should then share this information in order to break down organizational silos and remediate vulnerabilities on a timely basis.

More from

Who Carries the Weight of a Cyberattack?

Almost immediately after a company discovers a data breach, the finger-pointing begins. Who is to blame? Most often, it is the chief information security officer (CISO) or chief security officer (CSO) because protecting the network infrastructure is their job. Heck, it is even in their job title: they are the security officer. Security is their responsibility. But is that fair – or even right? After all, the most common sources of data breaches and other cyber incidents are situations caused…

Transitioning to Quantum-Safe Encryption

With their vast increase in computing power, quantum computers promise to revolutionize many fields. Artificial intelligence, medicine and space exploration all benefit from this technological leap — but that power is also a double-edged sword. The risk is that threat actors could abuse quantum computers to break the key cryptographic algorithms we depend upon for the safety of our digital world. This poses a threat to a wide range of critical areas. Fortunately, alternate cryptographic algorithms that are safe against…

Securing Your SAP Environments: Going Beyond Access Control

Many large businesses run SAP to manage their business operations and their customer relations. Security has become an increasingly critical priority due to the ongoing digitalization of society and the new opportunities that attackers exploit to achieve a system breach. Recent attacks related to corrupt data, stealing personal information and escalating privileges for remote code execution all highlight the new and varied entry points threat actors have taken advantage of. Attackers with the appropriate skills could be able to exploit…

Abuse of Privilege Enabled Long-Term DIB Organization Hack

From November 2021 through January 2022, the Cybersecurity and Infrastructure Security Agency (CISA) responded to an advanced cyberattack on a Defense Industrial Base (DIB) organization’s enterprise network. During that time frame, advanced persistent threat (APT) adversaries used an open-source toolkit called Impacket to breach the environment and further penetrate the organization’s network. Even worse, CISA reported that multiple APT groups may have hacked into the organization’s network. Data breaches such as these are almost always the result of compromised endpoints…