June 1, 2020 By David Bisson 2 min read

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

Unpacking the NIST cybersecurity framework 2.0

4 min read - The NIST cybersecurity framework (CSF) helps organizations improve risk management using common language that focuses on business drivers to enhance cybersecurity.NIST CSF 1.0 was released in February 2014, and version 1.1 in April 2018. In February 2024, NIST released its newest CSF iteration: 2.0. The journey to CSF 2.0 began with a request for information (RFI) in February 2022. Over the next two years, NIST engaged the cybersecurity community through analysis, workshops, comments and draft revision to refine existing standards…

What should Security Operations teams take away from the IBM X-Force 2024 Threat Intelligence Index?

3 min read - The IBM X-Force 2024 Threat Intelligence Index has been released. The headlines are in and among them are the fact that a global identity crisis is emerging. X-Force noted a 71% increase year-to-year in attacks using valid credentials.In this blog post, I’ll explore three cybersecurity recommendations from the Threat Intelligence Index, and define a checklist your Security Operations Center (SOC) should consider as you help your organization manage identity risk.The report identified six action items:Remove identity silosReduce the risk of…

Obtaining security clearance: Hurdles and requirements

3 min read - As security moves closer to the top of the operational priority list for private and public organizations, needing to obtain a security clearance for jobs is more commonplace. Security clearance is a prerequisite for a wide range of roles, especially those related to national security and defense.Obtaining that clearance, however, is far from simple. The process often involves scrutinizing one’s background, financial history and even personal character. Let’s briefly explore some of the hurdles, expectations and requirements of obtaining a…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today