Threat actor

Spring Ring

0 mentions in 7 days · 4 in 30 days · 4 total · first seen Aug 31, 2026 · last 12d ago

Timeline4 articles

ThreatsDay: CEO Phishing Kits, 5K Dropbox Account Hacks, OAuth Traps + 17 More Stories

Microsoft warns of Teams IT-impersonation intrusions deploying Node.js implants; Spring Ring vishing hit 150+ employees across 10 companies; The Gentlemen ransomware claims 683 victims.

Microsoft warned of a human-operated campaign abusing Teams external collaboration to impersonate IT help desk staff, deploy malicious MSI packages staging Node.js runtimes and obfuscated JavaScript implants, then pivot to domain controllers over WinRM. Unit 42 documented the Spring Ring vishing operation targeting over 150 employees across at least 10 companies using 26 attacker identities, including an NTLM relay variant against domain controllers. Sophos reported The Gentlemen ransomware (Gold Sherwood) reached 683 total victims by end of July 2026, adding 169 in July, with a playbook using BYOVD-based EDR killers and backup tampering. Group-IB found the Outsider phishing-as-a-service platform created 700+ new phishing pages within a month despite law enforcement takedowns.

The Hacker NewsSep 3, 18:02 UTC · 12d agoThreat actor in the wild1

Threat Gang 'Springs' Vishing Attacks on Microsoft Teams Users

The 'Spring Ring' operation uses vishing attacks against Microsoft Teams users to hijack sessions, deploy malware, and take over infrastructure.

Dark Reading reports on the Spring Ring threat gang conducting voice-phishing (vishing) attacks against users of Microsoft Teams. The operation aims to compromise collaboration-suite accounts to gain remote access to victim sessions, distribute malware, and potentially seize control of infrastructure. Further technical details were not provided in the available text.

Dark ReadingSep 2, 16:51 UTC · 13d agoPhishing & fraud

Vishing campaign abuses Microsoft Teams to give attackers a foothold in company networks

Unit 42 details 'Spring Ring', a vishing campaign using fake IT support on Microsoft Teams to reach 150+ employees at 10+ companies.

Palo Alto Networks Unit 42 documented 'Spring Ring', a voice-phishing campaign that ran January to April 2026, using 26 attacker identities and fake Microsoft 365 tenants such as 'ITProtectionDepartment' to impersonate internal IT support on Microsoft Teams. One path used Quick Assist or downloaded remote-support tools to run an obfuscated PowerShell script that disabled malware scanning before contacting C2; the other delivered a cloud-hosted file triggering browser hijacking, SMB internal network scanning, and a PetitPotam NTLM relay attempt against domain controllers to gain domain-level privileges. Both intrusion attempts were blocked before attackers reached their objectives. Collaboration-platform phishing alerts rose to 42% of Unit 42's telemetry in early 2026, up from 30%.

Help Net SecuritySep 1, 00:00 UTC · 14d agoPhishing & fraud in the wild

Spring Ring: An Inside Look at Voice Phishing Campaigns in Microsoft Teams

Unit 42 details the Spring Ring voice phishing campaign abusing Microsoft Teams to deploy malware and target enterprise domain controllers.

Palo Alto Networks Unit 42 analyzed the Spring Ring campaign, which abuses Microsoft Teams and voice phishing (vishing) to compromise enterprise users. Attackers use Teams calls to social-engineer victims, then deploy malware and advance toward enterprise domain controllers. The report documents the campaign's tactics and provides detection guidance for defenders.

Palo Alto Unit 42Aug 31, 10:00 UTC · 15d agoPhishing & fraud in the wild

Appears with

product Microsoft Teams 4 vendor Microsoft 4 vendor Palo Alto Networks 2 malware BlueKit 1 malware Obfuscated PowerShell script 1 malware The Outsider 1 organization iZOOlogic 1 organization Microsoft 1 organization Palo Alto Networks 1 organization Palo Alto Networks Unit 42 1 organization Unit 42 1 organization ZeroBEC 1 product Node.js 1 product PetitPotam 1 product Quick Assist 1 product ScreenConnect 1

Entities are extracted by the model from each article. Watching an entity keeps it in this browser only (no account); the watchlist page and dashboard alerts use it.