0% found this document useful (0 votes)
12 views4 pages

Chrome Malware: Dual Injection Threat

A sophisticated malware campaign has been discovered that bypasses Google Chrome's App-Bound Encryption using dual injection techniques, primarily targeting organizations in Vietnam's Telemarketing and Sales sectors. The malware executes fileless attacks via MSBuild.exe, maintains persistence through scheduled tasks, and communicates with attackers using the Telegram Web API to exfiltrate sensitive data. Recommendations for mitigation include user training, email filtering, application whitelisting, and deploying advanced threat detection solutions.

Uploaded by

nigeyis893
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
12 views4 pages

Chrome Malware: Dual Injection Threat

A sophisticated malware campaign has been discovered that bypasses Google Chrome's App-Bound Encryption using dual injection techniques, primarily targeting organizations in Vietnam's Telemarketing and Sales sectors. The malware executes fileless attacks via MSBuild.exe, maintains persistence through scheduled tasks, and communicates with attackers using the Telegram Web API to exfiltrate sensitive data. Recommendations for mitigation include user training, email filtering, application whitelisting, and deploying advanced threat detection solutions.

Uploaded by

nigeyis893
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Malware Bypasses Chrome App-Bound Encryption with Dual Injection

Document Control

Malware Bypasses Chrome App-Bound Encryption with Dual Injection

Document No:
Revision Status:
Effective Date:
Last Review Date:
Approved by
Preparer Name:
Signature
Date:

Document Revision History

Publication Date Author Revision No Change Description

Initial Document
Paul Shread -
Creation

Table of Contents

1. Introduction
2. Incident Overview
3. Attack Methodology
4. Indicators of Compromise (IoCs)
5. Recommendations
6. Conclusion
7. References
1. Introduction

Cyble researchers have discovered a sophisticated malware campaign that successfully bypasses
Google Chrome’s App-Bound Encryption using dual injection techniques. This malware can steal
sensitive user data, including login credentials and cookies, making it a severe threat to
organizations and individuals relying on Chrome’s security mechanisms.

2. Incident Overview

The malware primarily targets organizations in Vietnam, particularly in the Telemarketing and
Sales sectors. The exact initial infection method is unclear, but the attack starts with a ZIP file
containing a disguised LNK shortcut file and an XML project file. The malware sets up a scheduled
task running every 15 minutes to maintain persistence.
It leverages [Link] (a trusted Windows process) to execute fileless malware directly in
memory, making detection challenging.

3. Attack Methodology
Step 1: Initial Infection

• The malware is distributed via ZIP archives that contain:


o A LNK file disguised as a PDF
o An XML project file disguised as a PNG

Step 2: Execution & Persistence

• When the LNK file is executed, it:


o Copies the XML file to the Temp directory
o Creates a scheduled task that executes every 15 minutes
o Executes [Link] to load and run C# code from the XML project

Step 3: Dual Injection Technique

• Process Injection: Injects the malicious payload into legitimate system processes.
• Reflective DLL Injection: Loads and executes malicious DLLs directly in memory,
avoiding disk-based detection.

Step 4: Command & Control via Telegram Web API

• The malware uses Telegram Web API to:


o Establish communication with the attacker
o Exfiltrate sensitive user data such as encryption keys, cookies, and login credentials
o Dynamically switch bot ID and chat ID for ongoing control
• This method allows attackers to issue commands remotely, making the malware adaptable
and persistent.

4. Indicators of Compromise (IoCs)

• ZIP files containing disguised LNK and XML files


• Unusual scheduled tasks executing [Link]
• [Link] executing unsigned C# code from XML project files
• Suspicious outbound traffic to Telegram Web API endpoints
5. Recommendations

➢ User Training: Educate employees on the risks of opening unknown ZIP files and disguised
shortcuts.
➢ Email Filtering: Block LNK, ZIP, and XML attachments from untrusted sources.
➢ Application Whitelisting: Restrict execution of [Link] to prevent abuse.
➢ Limit Execution Paths: Configure policies to prevent execution from Temp and User
directories.
➢ Monitor Telegram API Activity: Watch for unexpected network connections to Telegram.
➢ Deploy EDR/XDR Solutions: Use tools like CrowdStrike Falcon to detect process
injection and fileless malware execution.
➢ Use Threat Intelligence Feeds: Integrate SIEM/EDR solutions to proactively detect threats.

6. Conclusion

This dual injection attack is a highly sophisticated and stealthy malware campaign that leverages
fileless execution, scheduled task persistence, and Telegram-based C2 communications.
Organizations must strengthen security policies, educate users, and deploy advanced threat
detection solutions to mitigate the risk effectively.

7. Reference

Cyble Blog Post:Malware Bypasses Google Chrome App-Bound Encryption

Common questions

Powered by AI

Organizations can mitigate risks by implementing comprehensive cybersecurity policies and deploying advanced technological solutions. Recommended policies include educating employees about the risks of unfamiliar ZIP files and disguised shortcuts, configuring email filters to block risky attachments, restricting MSBuild.exe execution, and monitoring Telegram API activities for unexpected connections. Deploying Endpoint Detection and Response (EDR) or Extended Detection and Response (XDR) solutions, like CrowdStrike Falcon, along with integrating Threat Intelligence feeds into security systems, enhances proactive threat detection and response capabilities .

The recommendations align closely with industry best practices, emphasizing user education, stringent email filtering, application whitelisting, and network traffic monitoring. These measures collectively address both technical and human vulnerabilities, reducing the attack surface for such sophisticated malware. Proactive monitoring and the integration of EDR/XDR solutions to track process anomalies and fileless activities further reflect best practices aimed at enhancing detection and response times, thus mitigating potential damages from breaches .

Key indicators of compromise include ZIP files containing disguised LNK and XML files, unusual scheduled tasks executing MSBuild.exe, MSBuild.exe running unsigned C# code from XML project files, and suspicious outbound traffic to Telegram Web API endpoints. Recognizing these IoCs allows for proactive threat detection by identifying unusual behaviors and network activities associated with the malware, thus enabling timely defensive responses .

The Telegram Web API serves a crucial role in the malware’s operation by establishing command and control (C&C) communications. It allows attackers to exfiltrate sensitive user data like encryption keys and credentials securely and dynamically switch bot ID and chat ID to maintain ongoing control. This use of a legitimate communication platform complicates detection while offering attackers a robust mechanism for remote command execution and threat persistence .

The malware discovered bypasses Google Chrome’s App-Bound Encryption using dual injection techniques, enabling it to steal sensitive user data such as login credentials and cookies. This breach of security mechanisms poses a significant threat to individuals and organizations relying on Chrome for secure communications. This exploitation allows attackers to access private data through the compromise of trusted encryption methods .

Failure to monitor and mitigate Telegram API activity can lead to undetected communication between the malware and its command and control servers, allowing attackers to exfiltrate sensitive data and maintain persistent access to compromised systems. Such persistent connections can result in ongoing data breaches, loss of sensitive information, and potential ransom or further exploitation of the compromised systems. By not monitoring these connections, organizations leave themselves vulnerable to extended and potentially damaging security incidents .

The attack methodology involves several key steps: initial infection through ZIP files with disguised LNK and XML files, execution and persistence via MSBuild.exe running fileless malware, and dual injection techniques involving process injection and reflective DLL injection. These techniques load malware directly into memory without writing to disk, complicating detection. Additionally, the use of Telegram Web API for communication enhances the malware's adaptability and persistence, posing significant challenges for traditional detection mechanisms focused on disk-based activity .

Fileless execution techniques, as used by this malware, present significant challenges to traditional security systems that typically rely on file-based signatures and anomaly detection. By executing code in memory without generating artifacts on the disk, these techniques evade detection and forensic analysis. This complicates both detection and remediation efforts, requiring the deployment of advanced behavioral monitoring and memory analysis tools to effectively identify and counteract such threats .

The initial infection vector involves ZIP files containing disguised LNK and XML files, though the exact mechanism of the initial infection remains unclear. The malware specifically targets organizations within the Telemarketing and Sales sectors in Vietnam, suggesting a focus on industries with valuable client data and potential economic impact. This targeting underlines the threat's strategic approach to compromising sectors where data exfiltration could lead to significant disruption .

The malware employs process injection by injecting malicious payloads into legitimate system processes, and reflective DLL injection by loading and executing malicious DLLs directly in memory. These techniques avoid writing the payload to disk, significantly enhancing stealth by evading traditional defenses that rely on file-based detection. By operating in memory, these injections enable the malware to execute undetected and maintain persistent control over the infected systems .

You might also like