Malicious Chrome Extension Steals Cookies and Credentials of Bank Customers


While going through new malware samples in our cloud we can across an interesting payload written in Delphi which unlike traditional banking Trojans uses a malicious chrome extension for stealing sensitive banking information from Banco do Brasil customers.

Main activity of this Trojan includes:

Downloads and installs Chrome extension files as .txt format
Search and modify target of all Google Chrome shortcuts to load malicious extension
Disables Google Chrome developer mode extension warning using code from Stackoverflow.
Targets Banco do Brasil ( and customers
Steals cookies and credentials using extension

Figure 1. Main Activity Flowchart


Delphi file contains URLs in the TEdit field, a timer to start activity and a button with an OnClick event that downloads Chrome extension files.

Figure 2. Delphi form

First, the callback on the FormShow event is triggered, which will get to the %APPDATA% path, decrypt the “/Microsoft/” string, and generate two random strings and connect them. After that, the timer callback triggers a button callback that, in turn, downloads the extension files from the server.

The button callback creates a directory structure path generated earlier by the FormShow callback and sets hidden attributes. It then downloads the remote files, also appends extension “.off” and sets a hidden and read-only attribute for these files.

Chrome extension files are downloaded from following URLs:


Delphi file checks to see if chrome is installed at “C:\Program Files\Google\Chrome\Application\chrome.exe” or “C:\Program Files (x86)\Google\Chrome\Application\chrome.exe”; it searches for all Google Chrome shortcuts in c:\ drive and if found, change their destination to “{chrome.exe path} –load-extension=%appdata%/{extension folder} –allow-running-insecure-content.” This way, whenever Chrome is run through these shortcut files, the malicious extension is loaded.

The Trojan will then download a batch script from the following location and executes it:


This batch script patches Google Chrome browser files to disable the developer mode extension warning that looks like:

Figure 3. Chrome developer mode extension warning

The above warning is shown by Chrome browser when any Chrome extension is loaded into the browser that is not signed and authorized by official Chrome webstore. The batch script is copied from a post on StackOverflow site:

Figure 4. Batch script for patching Google Chrome to disable warning

Before terminating, the malware connects to https://goo[.]gl/GxWtnE, a shortner URL leading to legitimate site[.]br (UOL is, the largest Brazilian content, digital services and technology company). We did not see any obvious reason for this request from our analysis other than generating legitimate traffic to blend in. At the time of our analysis there were total 631 hits on the shortened URL, most of which are probably victims, with some from sandboxes and analysts.

Whenever Chrome is run, it will start up loaded with the malicious extension and won’t show any popup warning. The extension will sit there waiting for the user to visit targeted sites. As soon as the user visits any of those sites, the extension will activate and set the proxy to redirect user traffic to the attackers server. The following are the extension details.

Figure 5. Malicious extension loaded in Google Chrome

Extension analysis

Figure 6. Extension manifest.json file

The manifest file is a JavaScript Object Notation (JSON) formatted file that must be present in every extension. It defines all permissions, scripts and URL expression matches and other important details about the extension. This manifest reveals much of the extension’s functionality. This extension poses as “Google Secure Web” extension with the description “Segurança para o seu navegador,” which translates to “Security for your browser.”

It requests following permissions:

“tabs” : Access to privileged fields of the tab objects used by several APIs, including the chrome.tabs APIs, to interact with the browser’s tab system. You can use this API to create, modify, and rearrange tabs in the browser.
“http://*/*,https://*/*, *://*/*”: All protocols and all URLs.
“webNavigation” : Access to the chrome.webNavigation API to receive notifications about the status of navigation requests in-flight.
“webRequest” : Access to the chrome.webRequest API to observe and analyze traffic and to intercept, block, or modify requests in-flight.
“webRequestBlocking” : Use of the chrome.webRequest API for blocking.
“Storage” : API to store, retrieve, and track changes to user data.
“cookies” : chrome.cookies API to query and modify cookies, and to be notified when they change
“activeTab” : The activeTab permission gives an extension temporary access to the currently active tab when the user invokes the extension, for example, by clicking its browser action. Access to the tab lasts until the tab is navigated or closed.
“proxy” : chrome.proxy API to manage Chrome’s proxy settings.

The manifest file specifies a wildcard for web_accessible_resources, sets “jquery.js” and “background.js” as background pages and “jquery.js” and “content.js” as content scripts to run on all frames of all web pages by injecting them at end of DOM.

Background pages are long-running code segments; when the extension is started the background page runs as long as the browser is running or when the extension is disabled.

Content Scripts are JavaScript files that run in the context of web pages; they can read or modify DOM.

It also specifies “*://*” and “*://**” as externally_connectable so that these web pages can connect to the extension via runtime.connect and runtime.sendMessage.

Background Script

Background script is obfuscated JavaScript code.

Figure 7. Obfuscated script

After deobfuscation, we can see human readable code as shown in Figure 8 and Figure 10.

This script adds two callbacks for messages received from the content script, and it acts on two commands, “prx” and “bj”: 

“prx” – sets “191.252.186[.]175:9595” as proxy.

Figure 8. Script code for setting proxy in Google Chrome

Figure 9. Proxy in action

“bj” : Steals session cookies for “[.]br” and sends to attacker controlled “novodominioxk01[.]asia/clientes.php” along with other data received from content script in following format:

“texto”: {data_from_extension} sessao= { “domain”: “”, “hostOnly”: true, “httpOnly”: false, “name”: “JSESSIONID”, “path”: “/”, “sameSite”: “no_restriction”, “secure”: false, “session”: true, “storeId”: “0”, “value”: “{cookie_value}”, “id”: 16}

Figure 10. Script code for sending stolen data to C&C

Content Script

Content script is also obfuscated similar to the background script and can be read after deobfuscation. If any of “[.]br,” “[.]br,” or ”[.]br” is visited, it will send the “prx” command to the background script, which will set proxy and, in the case of “[.]br,” will also inject JavaScript code in the web page to intercept a click with following button IDs “botao.acao.ok,” “botao.acao.assinar,” and “botao.acao.entrar” (translation “Button.Action.Ok, Sign, and Log In”).

Figure 11. Script code for sending “prx” command if required url is visited

When any of those buttons are clicked, it will intercept the click event, get the value of “senhaConta” (translation “passwordContact”) and ID “param” and send “bj” command to the background script with these values. It in turn sends these values and session cookies to the command and control (C&C) server.

Figure 12. Script code for sending intercepted data and “bj” command

String Decryption

Interesting strings in the malware are in encrypted format and it decrypts on the fly as per the requirement. The following python code can be used to decrypt strings:

Figure 13. Python code to decrypt strings

Encrypted and decrypted strings:

687488A106CE : chrome
26E0260A25B4E22E27A4F07DB58639EF49 : –load-extension=
2B2CC098812D4CBC6F8EA9B195360F826555157EF689BC964322517DF0DE550B2B : –allow-running-insecure-content
66B51E13261D8EEFF89CEA27 : manifest.txt
66B51E13261D8EEFF8829417FA : manifest.json
66B51E13261D8EEFF8829417FAE4CB96DF :
61EE8686DD229441DCBD : jquery.txt
61EE8686DD22945FAC : jquery.js
61EE8686DD22945FAC07C79554 :
69A10DED4EA4045442828506E420 : background.txt
69A10DED4EA404544282851855 : background.js
69A10DED4EA404544282851855A213484E :
6873389F03983CBFF2C15C : content.txt
6873389F03983CBFEC92 : content.js
6873389F03983CBFEC92489941A7 :
48A2400D0B5D78620FCC355BAFD7FDE08C4DD0027AF3967944909FD82AC18047A0DE7EE37BFD1A7F15F281E791036A553D3797A30A : C:\Program Files\Google\Chrome\Application\chrome.exe
48A2400D0B5D78620FCC355BAFD7FDE0F00D4D4E3F6671721952E44159960D83822C738AEEFE6F73B7B7E7D361A8E0950E1D38E5EA1D3638878F51 : C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
687488A106CE272628ED : chrome.dll
69A1404370F7 : ba.txt
254B4A8B : .bat
7FA8565288971357 : trocakid
577B46B70F74CBE606F6A2 : \Microsoft\
6393A7C1048E6B935ABD84437B796BB93F5A643AA7 :



This is a Security Bloggers Network syndicated blog post authored by Read the original post at: Research Blog