Saturday, March 22, 2025
HomeCyber Security NewsVulnerable Exchange Server Hit by Squirrelwaffle Malware Loader

Vulnerable Exchange Server Hit by Squirrelwaffle Malware Loader

Published on

SIEM as a Service

Follow Us on Google News

Squirrelwaffle malware has been found in existence since the mid of September 2021. This malware is designed to cause chain infections. The Rapid Response Team at Sophos has recently discovered that the Squirrelwaffle malware loader used ProxyLogon and ProxyShell exploits for targeting Microsoft Exchange Server.

After gaining access to the vulnerable server, the attackers used the email thread hijacking technique which involves inserting malicious replies into Employees’ existing email threads to distribute the Squirrelwaffle malware to both internal and external recipients.

When they monitored further, they found that the vulnerable server was not only used for malicious spam campaigns but also for a financial fraud attack by extracting information from a stolen email thread.

Squirrelwaffle

Squirrelwaffle is a type of malware loader distributed via spam campaigns as a malicious office document. This provides information about the victim’s environment and with a channel that can be used to deliver and infect with other malware. 

When a victim opens the malicious office document and enables macros, it downloads a VB script and executes Cobalt Strike Beacons which give control over the victim’s machine.

The Investigation

Usually, the Squirrelwaffle attack is ended when the defenders detect and remediate by providing patches to the vulnerable servers. But in the recent set of events, such remediation measures wouldn’t have stopped the financial fraud attack as they have already exported an email thread about customer payment from the victim’s exchange server. Hence it is recommended to investigate further for other impacts.

Typo-squatted domains were registered and used by the attackers for email thread replies.

The registered domain appears similar to the original victim’s domain but with a small typo that is often not noticed by the victims. Once they convince the victims, they use these email threads to redirect the payments.
Image

To provide additional legitimacy to the victims, they used additional email addresses from the typo-squatted domain and added them in CC of the reply emails. Just like every other phishing campaign, these attackers also provide a sense of urgency to the victims.

Prevention

It is advised to keep the Microsoft Exchange Servers updated and patched to prevent any type of compromise. Industry-recognized prevention methods such as SPF records, DKIM, and DMARC records must be standard to stop phishing campaigns. It is also necessary to provide knowledge to all the employees about Phishing attempts.

You can follow us on Linkedin, Twitter, Facebook for daily Cybersecurity updates.

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

Attackers Leverage Weaponized CAPTCHAs to Execute PowerShell and Deploy Malware

In a recent surge of sophisticated cyberattacks, threat actors have been utilizing fake CAPTCHA...

Researchers Uncover FIN7’s Stealthy Python-Based Anubis Backdoor

Researchers have recently discovered a sophisticated Python-based backdoor, known as the Anubis Backdoor, deployed...

Researchers Reveal macOS Vulnerability Exposing System Passwords

A recent article by Noah Gregory has highlighted a significant vulnerability in macOS, identified...

JumpServer Flaws Allow Attackers to Bypass Authentication and Gain Full Control

JumpServer, a widely used open-source Privileged Access Management (PAM) tool developed by Fit2Cloud, has...

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

Attackers Leverage Weaponized CAPTCHAs to Execute PowerShell and Deploy Malware

In a recent surge of sophisticated cyberattacks, threat actors have been utilizing fake CAPTCHA...

Researchers Uncover FIN7’s Stealthy Python-Based Anubis Backdoor

Researchers have recently discovered a sophisticated Python-based backdoor, known as the Anubis Backdoor, deployed...

Researchers Reveal macOS Vulnerability Exposing System Passwords

A recent article by Noah Gregory has highlighted a significant vulnerability in macOS, identified...