Trojan.TrickBot is Malwarebytes’ detection name for a banking Trojan targeting Windows machines.
Developed in 2016, TrickBot is one of the more recent banking Trojans, with many of its original features inspired by Dyreza (another banking Trojan). Besides targeting a wide array of international banks via its webinjects, Trickbot can also steal from Bitcoin wallets.
Some of its other capabilities include harvesting emails and credentials using the Mimikatz tool. Its authors also show an ability for constant new features and developments.
Trojan.TrickBot comes in modules accompanied by a configuration file. Each module has a specific task like gaining persistence, propagation, stealing credentials, encryption, and so on. The C&Cs are set up on hacked wireless routers.
The endpoint user will not notice any symptoms of a Trickbot infection. However, a network admin will likely see changes in traffic or attempts to reach out to blacklisted IPs and domains, as the malware will communicate with Trickbot’s command and control infrastructure to exfiltrate data and receive tasks.
Trojan.TrickBot gains persistence by creating a Scheduled Task.
Trojan.TrickBot focuses on stealing banking information.
TrickBot typically spreads via malicious spam campaigns. It can also spread laterally using the EternalBlue exploit (MS17-010).
Other methods of propagation include infected attachments and embedded URLs. Trojan.TrickBot is also seen as a secondary infection dropped by Trojan.Emotet.
Due to the way Trickbot uses the EternalBlue vulnerability to spread through a company’s network, any infected machine on the network will re-infect machines that have been previously cleaned when they rejoin the network. Therefore, IT teams need to isolate, patch, and remediate each infected system one-by-one. This can be a long and painstaking process.
Malwarebytes protects business and home users from Trojan.Trickbot with our signature-less anti-exploit technology.
Malwarebytes can also protect users from Trojan.TrickBot with our real-time protection.
Malwarebytes can detect and remove Trojan.TrickBot on business endpoints without further user interaction. But to be effective on networked machines, you must first follow these steps:
Identifying the infected machines
If you have unprotected endpoints/machines, you can run Farbar Recovery Scan Tool (FRST) to look for possible Indicators of Compromise (IOC). Besides verifying an infection, FRST can also be used to verify removal before bringing an endpoint/machine back into the network.
Disabling Administrative Shares
Windows server shares by default install hidden share folders specifically for administrative access to other machines. The Admin$ shares are used by Trickbot once it has brute forced the local administrator password. A file share sever has an IPC$ share that Trickbot queries to get a list of all endpoints that connect to it. These AdminIP shares are normally protected via UAC, however, Windows will allow the local administrator through with no prompt.
The most recent Trickbot variants use C$ with the Admin credentials to move around and re-infect all the other endpoints.
Repeated re-infections are an indication the worm was able to guess or brute force the administrator password successfully. Please change all local and domain administrator passwords.
It is recommended to disable these Admin$ shares via the registry, as discussed here. If you do not see this registry key, it can be added manually and set up to be disabled.
To remove the Trickbot Trojan using Malwarebytes business products, follow the instructions below.
If you have infected machines that are not registered endpoints in Malwarebytes Endpoint Protection, you can remove Trickbot with our Breach Remediation tool (Malwarebytes Incident Response).
Malwarebytes can detect and remove Trojan.Trickbot without further user interaction.
Trojan.Trickbot typically creates a folder under %APPDATA%\Roaming to park its modules:
%APPDATA%\roaming\winapp\.exe for example:
%APPDATA%\roaming\winapp\client_id for example:
%APPDATA%\roaming\winapp\group_tag for example:
%APPDATA%\system32\Tasks\services update for example:
%APPDATA%\system32\Tasks\MsSysToken for example:
19CA05FC17F0128 or similar looking Mutex name.