Researchers have documented a recent phishing campaign targeting online banking users which masquerades as Google in its attempt to steal valuable credentials.
According to cybersecurity researchers from Sucuri, the attack wave against a Polish bank and its users is impersonating Google reCAPTCHA systems and panic-eliciting techniques to prompt victims to click on malicious links embedded in scam emails.
The emails in question contain a fake confirmation for a recent transaction, alongside a link to a malicious .PHP file.
Messages sent to would-be victims ask them to 'verify' these non-existent transactions by clicking on the link.
This attack method is nothing new, but the next stage is somewhat more unusual. If a victim fails to realize the message is fake and clicks on the link, they are not sent to a standard, fake replica of the bank, but rather the PHP file serves a fake 404 error page.
"This page does a decent job at replicating the look of Google's reCAPTCHA, but since it relies on static elements, the images will always be the same unless the malicious PHP file's coding is changed," the researchers say. "It also doesn't support audio replay, unlike the real version."
The browser agent is then re-checked to ascertain how the victim has visited the page. A .zip dropper is on offer, alongside a malicious .APK reserved for Android users who fill in the CAPTCHA and download the payload.
Samples of the malware have been uploaded to VirusTotal. The malware is most often found in the wild in its Android form and is able to read a mobile device's state, location, and contacts; scan and send SMS messages, make phone calls, record audio, and steal other sensitive information.
The Trojan is detected as Banker, BankBot, Evo-gen, Artemis, and more by antivirus software.
In January, researchers from Trend Micro uncovered an interesting campaign relating to the Anubis banking Trojan. The team found two apps in the Google Play store, a currency converter and power saver, which were laden with malware which would only trigger when a user moved their device.
By using motion sensor data as a catalyst for execution, the Trojan attempted to prevent discovery by researchers making use of sandbox environments.