Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

ABTV

5/29/2019
06:00 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

HawkEye Malware Finds Renewed Life With Financially Motivated Actors

IBM X-Force researchers have reported an increase in the HawkEye v9 keylogger infection campaigns after they looked at data from the IBM X-Force effort during April and May 2019.

IBM X-Force researchers have reported an increase in the HawkEye v9 keylogger infection campaigns after they looked at data from the IBM X-Force effort during April and May 2019.

The researchers found that the older, but still potent, malware is targeting businesses around the world. Malicious third parties have long appreciated that the malware has a good reputation for its abilities as a dropper of other payloads (along with the key logging it can do) via botnets that can be controlled on its behalf. These botnets-as-a-service have been a longstanding revenue stream for those who have sold HawkEye over the past six years.

Those behind the malware have seemed to be financially motivated from the beginning, selling the malware as well as providing software updates so it would be considered to be a "commercial" product. If the data they got from the tool wouldn't make them a score, then they would sell the tool instead.

So, there are many HawkEye customers out there who can implement differing campaigns from many differing locations. It's not just a single threat actor, but all of the actors that are popping up alongside HawkEye do seem to be alike in that they are -- like the original author -- financially motivated.

Businesses have the money honey to attract an attack from this kind of bad guy. This should not come as a big surprise.

X-Force saw that in April 2019, HawkEye campaigns were aimed at many different business sectors including transportation and logistics, healthcare, import and export, marketing, agriculture, as well as others.

The IP addresses that originated the malspam came from Estonia, while users were targeted in countries around the globe. IP origin is not a reliable detector of a threat actor's location.

The businesses were initially attacked with a wave of social engineering. X-Force says that the malspam messages came disguised as an email from a large bank in Spain, but "other messages carrying HawkEye infections came in various formats, including fake emails from legitimate companies or from other banks."

Financially motivated, indeed. Companies and banks give them the initial shelter they want, so that they are able to gain entry to the workplace unnoticed. If you have previously dealt with some organization, social engineers hope that the trust barriers between you and the organization are less raised and that you will be more likely to click that link.

HawkEye wasn't always so active. It sort of went zombie in 2017, then reappeared in 2018 as "Hawkeye Reborn v8." It may have gotten a new owner-operator around the same time, since it was rapidly renamed "Hawkeye Reborn v9."

But however it changes as it goes on, security defenses will have to adjust.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...