Malware Alert

A new and sophisticated malware campaign is targeting corporate networks by exploiting Microsoft Teams voice calls. Threat actors are impersonating IT support staff to trick employees into installing malware, giving them initial access to sensitive company data.

The Attack Vector

The campaign begins with a phishing email containing a malicious PDF attachment disguised as an 'Employee Survey'. Shortly after opening the document, the victim receives a Microsoft Teams voice call from an external account impersonating a 'System Administrator'.

The attackers use the Teams voice call to convince the victim to grant remote control via Microsoft Teams' built-in screen-sharing feature. They then guide the victim through installing legitimate remote-access tools, which are later used to download and execute malicious software.

Malware Installation

The attackers download and execute a malicious MSI installer, which acts as a malware loader. This loader downloads a legitimate Node.js runtime, decrypts embedded payloads, and ultimately launches the EtherRAT malware.

EtherRAT Malware

EtherRAT is a cross-platform remote access trojan written in Node.js that gives attackers full control over compromised systems. The malware can execute commands, manipulate files, steal data, and maintain persistence.

Execute commands on compromised systems
Manipulate files and steal data
Maintain persistence and evade detection
Use Ethereum smart contracts to retrieve its active command-and-control server

Prevention and Protection

To protect against this malware campaign, companies should educate their employees on the risks of phishing emails and suspicious Microsoft Teams voice calls. Implementing robust security measures, such as multi-factor authentication and regular software updates, can also help prevent malware infections.

Conclusion

Technology teams are watching malware alert closely because changes in this space often arrive faster than internal policies can adapt.

For product and engineering leaders, the practical question is how this could reshape roadmaps, vendor choices, and security reviews over the next few quarters.

Organizations that document lessons early tend to respond more calmly when similar patterns appear again.

In many companies, the first impact shows up in planning meetings: teams reassess priorities, revisit risk registers, and check whether existing tooling still fits.

Smaller businesses feel these shifts too. A single platform change or market move can affect customer trust, delivery timelines, and hiring plans.

The most resilient teams treat stories like this as input for quarterly reviews rather than one-day headlines.

If your business depends on modern software, ERP, VoIP, or customer-facing apps, staying informed helps you separate noise from decisions that require action.

Looking ahead, disciplined follow-through matters: assign owners, set review dates, and measure whether your response improved outcomes.

Security and compliance stakeholders should ask whether current controls still match the pace of change described in this update.

Operations leaders can reduce friction by translating the headline into a short internal brief with clear next steps for each department.

Customer support teams may see early signals through tickets, outages, or policy questions long before leadership reviews are scheduled.

Finance and procurement groups should note whether licensing, vendor risk, or implementation costs need revisiting after this development.

Training programs benefit from timely updates so staff understand what changed, what did not change, and what requires escalation.

Architecture reviews are a practical place to test assumptions, especially when new tools, platforms, or threats enter the conversation.

Documentation quality often determines how quickly a company recovers from surprises; capture decisions while context is still clear.