Sunday, December 15, 2024
HomeCyber Security NewsVulnerable Exchange Server Hit by Squirrelwaffle Malware Loader

Vulnerable Exchange Server Hit by Squirrelwaffle Malware Loader

Published on

SIEM as a Service

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.

- Advertisement - SIEM as a Service

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

“Password Era is Ending,” Microsoft to Delete 1 Billion Passwords

Microsoft has announced that it is currently blocking an astounding 7,000 password attacks every...

Over 300,000 Prometheus Servers Vulnerable to DoS Attacks Due to RepoJacking Exploit

The research identified vulnerabilities in Prometheus, including information disclosure from exposed servers, DoS risks...

Reyee OS IoT Devices Compromised: Over-The-Air Attack Bypasses Wi-Fi Logins

Researchers discovered multiple vulnerabilities in Ruijie Networks' cloud-connected devices. By exploiting these vulnerabilities, attackers...

New Android Banking Malware Attacking Indian Banks To Steal Login Credentials

Researchers have discovered a new Android banking trojan targeting Indian users, and this malware...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

“Password Era is Ending,” Microsoft to Delete 1 Billion Passwords

Microsoft has announced that it is currently blocking an astounding 7,000 password attacks every...

Over 300,000 Prometheus Servers Vulnerable to DoS Attacks Due to RepoJacking Exploit

The research identified vulnerabilities in Prometheus, including information disclosure from exposed servers, DoS risks...

Reyee OS IoT Devices Compromised: Over-The-Air Attack Bypasses Wi-Fi Logins

Researchers discovered multiple vulnerabilities in Ruijie Networks' cloud-connected devices. By exploiting these vulnerabilities, attackers...