An RMM phishing campaign initially associated with Canadian targeting due to its use of Canada Revenue Agency (CRA) tax forms as lures has turned out to be part of a broader campaign spanning 46 countries.
Around 45% of observed activity was associated with the United States, making it the campaign’s top geographic target. ANY.RUN research connected 601 cases to the wider operation, which uses fake documents to trick victims into installing legitimate remote monitoring and management (RMM) software.
The attackers adapt their lures to different targets, using shipping and UPS communications, Adobe PDFs, tax notices, US Social Security Administration themes, invoices, and other documents. Rapidly rotated, disposable Vercel infrastructure makes the campaign harder to track and detect.
US-First Threat with Daily Infrastructure Rotation
 |
| Threat overview by ANY.RUN |
The campaign’s infrastructure changes significantly faster than its attack pattern. ANY.RUN researchers identified 425 kit URLs across 240 hosts, 94% of which were observed for only a single day.
The operation has used Vercel, GitHub Pages, Netlify, compromised websites, and other infrastructure for delivery. Payloads have also been staged through services including Amazon S3, Cloudflare R2, GitHub, DigitalOcean Spaces, Dropbox, and GoFile.
Despite this rapid rotation, the phishing kit leaves more persistent fingerprints. Shared assets such as font1.woff2, recurring image resources, and the secure.html → project/*.zip delivery structure helped researchers connect otherwise separate infrastructure to the same campaign.
Education, technology, and government are among the top targeted industries. Banking, finance, and manufacturing are also prominently present.
 |
| Attack chain overview by ANY.RUN |
Individual domains and RMM products are disposable, while the underlying delivery chain is more stable. This shows why detection cannot depend solely on malware verdicts, reputation, or individual IOCs.
To detect these patterns and distinguish legitimate RMM use from abuse, SOC teams need access to the full behavioral context behind suspicious activity.
Respond faster and reduce risk in your company with deeper visibility and intel from 16K+ organizations. Power your SOC with ANY.RUN
Key Detection Takeaways for SOC Teams
- Build a product-agnostic defense: legitimate software can be abused and switched between vendors, leading to visibility gaps. Maintain focus on delivery chain and unauthorized remote-access activity.
- Detect around campaign patters: Instead of relying only on domains, which in this campaign get rotated daily, prioritize more stable kit indicators, including the fmtt / font1.woff2, icons8-microsoft-word-94.png asset, and the secure.html → project/*.zip chain.
- Establish mail-layer controls and raise user awareness: SOC teams should account for password-protected archive delivery.
- Give analysts behavioral and threat context: ANY.RUN’s Interactive Sandbox exposed the campaign’s browser activity, scripts, processes, downloads, and network behavior, while Threat Intelligence Lookup connected persistent indicators to related infrastructure and cases.
 |
| One of the lures, an Adobe phishing page, analyzed within ANY.RUN Interactive Sandbox |
As attackers increasingly combine legitimate software, trusted services, and disposable infrastructure, security teams need to access and operationalize in-depth threat context.
