Stopping a Banking Trojan in Its Tracks

From Hacking Demo to Real-Life Scenario

The situation was eerily similar to a Huntress workshop James had previously attended; a session that was designed to highlight these exact types of threats.

An end user received a somewhat-suspicious attachment and attempted to open it, but stopped short of enabling macros. They forwarded the doc to a second user, who did open it and unknowingly unleashed Qakbot—a banking trojan capable of logging keystrokes, harvesting browser credentials and self-propagating throughout a network.

One of the challenges with Qakbot is that it’s designed specifically to bypass preventive security tools like antivirus and DNS filtering.

That’s when the Huntress platform jumped into action. By identifying and analyzing newly created Windows autostarting code, Huntress determined Qakbot was in play—and a SOC engineer generated an incident report which explained what had happened and how to fix it.

Moments later, the end user realized their mistake and sent an email to Binatech—where James and his team were already working to resolve the issue.

“We were taking remediation steps before that user’s email hit our inbox,” he said. “The alert from Huntress gave us a clear understanding of what we were dealing with and which user was affected, which made it easy for us to respond right away. The platform truly delivered in this scenario—we were able to disconnect the machine and reset every password the user was tied to—all within twenty minutes of receiving the initial alert.”

“In addition to stopping the threat, Huntress really helped us demonstrate our value to the client,” he added. “It ultimately even helped us upsell some additional services.”

Without Huntress enabled, the attack could’ve played out quite differently. “Who knows how long it would’ve taken to remediate, assuming we’d found the banking Trojan,” Otis explained. “The real question is how much money would have been lost had the Trojan successfully extracted bank account info—that’s the part we’re grateful to not have to deal with.”

‍

The alert from Huntress gave us a clear understanding of what we were dealing with and which user was affected, which made it easy for us to respond right away. The platform truly delivered in this scenario—we were able to disconnect he machine and reset every password the user was tied to—all within twenty minutes of receiving the initial alert.

Finding Huntress

While Binatech had done some early testing with Huntress, the company was initially using an endpoint detection and response (EDR) tool and decided they didn’t need to include Huntress as part of their security stack. That changed when the EDR’s alerts started piling up.

“We were experiencing some growing pains for a few months and issues with false positives, so I was questioning what I was paying for,” Otis recalled. “We took a second look at Huntress, and with some of its newer services like Assisted Remediation the decision to switch back was an easy one.”

Assisted Remediation offers one-click execution of corrective actions when malicious footholds are detected. It’s one of several ways Huntress enables its partners to respond quickly—and accurately—to discovered threats.

‍