Wednesday, April 2, 2025
HomeCyber AttackHackers Deliver AsyncRAT Through Weaponized WSF Script Files

Hackers Deliver AsyncRAT Through Weaponized WSF Script Files

Published on

SIEM as a Service

Follow Us on Google News

The AsyncRAT malware, which was previously distributed through files with the .chm extension, is now being disseminated via WSF script format. The WSF file was found to be disseminated in a compressed file (.zip) format through URLs included in emails.

AsyncRAT spreads through a variety of strategies and tactics. Malspam and phishing efforts, which mimic legitimate messages like DHL shipment updates with malicious file attachments, are the most prevalent infection vectors.

Threat actors are still creating and using cutting-edge and unique ways to spread AsyncRAT, such as “fileless” injection, which loads the main AsyncRAT binary into memory and runs it without requiring the target system to have a file installed.

How is the AsyncRAT Disseminated via WSF Script?

The AhnLab Security Emergency Response Center (ASEC) reports that the downloaded zip file is decompressed to produce a file with the .wsf file extension. 

This file just has one <script> tag in the middle and is primarily made up of comments, as seen in the image below.

https://i0.wp.com/asec.ahnlab.com/wp-content/uploads/2023/11/image-81.png?resize=702%2C360&ssl=1
The download link in the WSF script

Upon executing this script, a Visual Basic script is downloaded and executed. From the same C2 address, this script downloads a.jpg file, which is a zip file masquerading as a jpg file.

https://i0.wp.com/asec.ahnlab.com/wp-content/uploads/2023/11/image-97.png?resize=1024%2C361&ssl=1
The attack flow

It then converts this jpg file’s extension to.zip before decompressing it. An XML file containing the command string to launch the Error.vbs file included in the compressed file is produced and executed using PowerShell

Before loading and running the binary, the last file to be executed, pwng.ps1, converts the contained strings into a.NET binary.

https://i0.wp.com/asec.ahnlab.com/wp-content/uploads/2023/11/image-98.png?resize=1024%2C511&ssl=1
PowerShell script launching a fileless attack

Three obfuscated variables are used in these phases such as:

  • $jsewy: Malware that performs the features of AsyncRAT 
  • $jsewty: Malware that performs the injection feature
  • $KRDESEY: The process the malware is injected into

“The malware executed in the end is identified as AsyncRAT which has information exfiltration and backdoor features”, researchers said.

Recommendation

The threat actor uses complex fileless techniques without the need for EXE files to spread the same malware in different ways.

When opening files or external links from emails, users should always exercise caution. Users are advised to utilize security product monitoring tools to recognize and block access from threat actors.

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Firefox 137 Launches with Patches for High-Severity Security Flaws

Mozilla has officially launched Firefox 137 with crucial security fixes aimed at addressing several...

Google Cloud Platform Vulnerability Exposes Sensitive Data to Attackers

A privilege escalation vulnerability in Google Cloud Platform (GCP), dubbed "ImageRunner," was recently discovered...

Apple Fined $162 Million by France Authorities for Mobile Ad Market Domination

French antitrust regulators have imposed a hefty fine of €150 million ($162.4 million) on...

20,000 WordPress Sites at Risk of File Upload & Deletion Exploits

A critical security alert has been issued to WordPress site administrators following the discovery...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Firefox 137 Launches with Patches for High-Severity Security Flaws

Mozilla has officially launched Firefox 137 with crucial security fixes aimed at addressing several...

Google Cloud Platform Vulnerability Exposes Sensitive Data to Attackers

A privilege escalation vulnerability in Google Cloud Platform (GCP), dubbed "ImageRunner," was recently discovered...

Apple Fined $162 Million by France Authorities for Mobile Ad Market Domination

French antitrust regulators have imposed a hefty fine of €150 million ($162.4 million) on...