{ "id": "572b46b4-9e18-4d01-a805-9f3146ea84ed", "created_at": "2026-04-06T00:10:07.987536Z", "updated_at": "2026-04-10T03:30:33.917898Z", "deleted_at": null, "sha1_hash": "e5352865174fa10830c046704dca3f5cdc80c2ce", "title": "TeaBot Banking Trojan Posted as QR Code app in Google Play Store Targeting US Users", "llm_title": "", "authors": "", "file_creation_date": "0001-01-01T00:00:00Z", "file_modification_date": "0001-01-01T00:00:00Z", "file_size": 1759579, "plain_text": "TeaBot Banking Trojan Posted as QR Code app in Google Play\r\nStore Targeting US Users\r\nBy Gurubaran\r\nPublished: 2022-03-03 · Archived: 2026-04-05 17:30:36 UTC\r\nAt the beginning of 2021, a new type of trojan called “Teabot” was found attacking users. The trojan was\r\nspecifically designed to steal the victim’s bank credentials and SMS messages.\r\nOther features of the trojan included Remote access capabilities and screen capturing via request-on-demand\r\nservices. Threat actors have the ability to do account takeovers directly from compromised mobile devices. This\r\ntechnique is called “On-device fraud”.\r\nTeabot trojan was distributed through smashing campaigns where attackers used a lure list such as VLC media\r\nplayer, TeaTV, DHL and UPS, etc. Recent researches show that hackers have used the Google Play store to\r\ndistribute the “dropper applications”.\r\nReports suggest that the target list has expanded further including 400 applications that involve various banks,\r\ncrypto exchanges or wallets, and digital insurances in countries like the US, Russia, and Hong Kong.\r\nEvolution and Distribution of TeaBot\r\nIn its initial stages in 2021, TeaBot was not fully developed. Nevertheless, hackers were distributing it through\r\nsmashing campaigns as mentioned before. Later, the trace was lost and the malware was found to be non-existent\r\nuntil February 21, 2022. \r\nResearchers at Cleafy were able to take a glimpse of a particular application that was published on the Google\r\nPlay store. Reviews seemed very legitimate with almost 10,000+ downloads. However, this application was found\r\nto be a TeaBot dropper application. The dropper was delivering TeaBot through fake update procedures. \r\nhttps://gbhackers.com/teabot-banking-trojan/\r\nPage 1 of 5\n\nThe application was a QR code and Barcode Scanner Application published under the name “QR BarCode\r\nScanner Bussiness LLC”. Users were giving feedback that the app was good and well-functioning. The dropper\r\nwas hiding behind the QR code scanner.\r\nOnce the victims install and open the app through the Google Play store, the app gives a pop-up message that an\r\nupdate must be installed. When victims click on install, the application downloads the dropper and installs another\r\napplication on the victim’s device.\r\nLegitimate Play store apps will redirect to Google play store for any updates. The installed application was found\r\nto be TeaBot trojan.\r\nSource : Cleafy\r\nhttps://gbhackers.com/teabot-banking-trojan/\r\nPage 2 of 5\n\nCleafy labs reported that the second application which was named QR Code Scanner: Add-on is downloaded\r\nfrom two particular Github repositories owned by the user feleanicusor.\r\nOn exploring further, the repositories had so many samples of TeaBot dated from Feb 17, 2022.\r\nSource : Cleafy\r\nAttack Chain of TeaBot\r\nTeabot’s attack chain clearly states that attackers have been working on the sideloading and evasive techniques\r\nwhich start from the initial dropper application to the hosting of the malicious payload. \r\nWhen the victims accept the download of the fake update, TeaBot installation procedures take place. During the\r\ninstallation, it also asks for Accessibility services permission to get necessary privileges. The application\r\nspecifically asks for 2 permissions.\r\nView and control Screen – This permission is acquired to view and control the screen on the victim’s\r\ndevice which is used for obtaining login credentials, 2FA codes, and to read SMS.\r\nView and Perform actions – This permission is described as interaction with an app. But actually, it is\r\nrequired to perform malicious actions with the infected device.\r\nhttps://gbhackers.com/teabot-banking-trojan/\r\nPage 3 of 5\n\nSource : Cleafy\r\nA full detailed report on how threat Actors used strong obfuscation techniques to evade antivirus software was\r\npublished by Cleafy.\r\nYou can follow us on Linkedin, Twitter, Facebook for daily Cybersecurity and hacking news updates.\r\nhttps://gbhackers.com/teabot-banking-trojan/\r\nPage 4 of 5\n\nGurubaran\r\nGurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience\r\nas a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.\r\nSource: https://gbhackers.com/teabot-banking-trojan/\r\nhttps://gbhackers.com/teabot-banking-trojan/\r\nPage 5 of 5", "extraction_quality": 1, "language": "EN", "sources": [ "Malpedia" ], "references": [ "https://gbhackers.com/teabot-banking-trojan/" ], "report_names": [ "teabot-banking-trojan" ], "threat_actors": [ { "id": "75108fc1-7f6a-450e-b024-10284f3f62bb", "created_at": "2024-11-01T02:00:52.756877Z", "updated_at": "2026-04-10T02:00:05.273746Z", "deleted_at": null, "main_name": "Play", "aliases": null, "source_name": "MITRE:Play", "tools": [ "Nltest", "AdFind", "PsExec", "Wevtutil", "Cobalt Strike", "Playcrypt", "Mimikatz" ], "source_id": "MITRE", "reports": null } ], "ts_created_at": 1775434207, "ts_updated_at": 1775791833, "ts_creation_date": 0, "ts_modification_date": 0, "files": { "pdf": "https://archive.orkl.eu/e5352865174fa10830c046704dca3f5cdc80c2ce.pdf", "text": "https://archive.orkl.eu/e5352865174fa10830c046704dca3f5cdc80c2ce.txt", "img": "https://archive.orkl.eu/e5352865174fa10830c046704dca3f5cdc80c2ce.jpg" } }