Ransomware Attacks

A new wave of cyberattacks is targeting North American organizations, using Microsoft Teams to gain remote access to corporate devices and deploy ransomware. The attackers impersonate IT support staff, tricking employees into granting them access to sensitive systems.

The Attack Method

The attacks begin with external Microsoft Teams accounts impersonating IT helpdesk or support personnel in Teams chats and voice calls to targeted employees. These calls can last anywhere from 90 seconds to over 20 minutes, with most being completed in approximately two to two-and-a-half minutes.

Targeted Industries

The threat actors targeted organizations across numerous sectors, with services, manufacturing, energy, and construction and engineering experiencing the largest number of attacks. At least three of these intrusions led to the deployment of Chaos ransomware, with one attack going from initial access to encrypting files in less than 17 hours.

Domain Manipulation

The attackers created IT-themed domains under the '.top' top-level domain to initiate communication. Examples of these domains include sequrityupdate.top, scan-security.top, system-connect.top, and supportsoft.top. They paired these domains with fake IT support people using specific aliases.

Prevention Measures

To prevent such attacks, it's essential to educate employees on the risks of social engineering and the importance of verifying the identity of IT support staff. Organizations should also implement robust cybersecurity measures, including multi-factor authentication and regular security audits.

Key Takeaways

Technology teams are watching ransomware attacks 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.