ARToken: An Affiliate Phishing Panel That Turns Vendor Invoice Emails into Microsoft 365 Takeovers
ARToken sends vendor invoice emails, captures Microsoft 365 tokens through device code phishing and gives operators tools for invoice fraud from the stolen mailbox.

AegisAI Threat Watch · Device code phishing
ARToken: An Affiliate Phishing Panel That Turns Vendor Invoice Emails into Microsoft 365 Takeovers
An EvilTokens affiliate panel sends vendor invoice emails, captures Microsoft 365 tokens through device code phishing and gives operators tools to run business email compromise.
Analysis based on 1 July 2026 reporting by The Register, Help Net Security and BleepingComputer on research into the ARToken panel, plus a 26 October 2026 update from The Hacker News. The original research report is not linked; every fact below is cited to these outlets or to a standards or documentation page.
ARToken is an EvilTokens affiliate panel that sends vendor invoice emails, captures Microsoft 365 tokens through device code phishing and gives operators built-in tools for business email compromise. Researchers found it during an incident response engagement.
The sign-in is genuine, so the password and the MFA prompt both pass on Microsoft's side. What the operator receives is a token, and the panel can turn it into longer-lived access. The reporting does not say how many organizations were reached.
Sources: Help Net Security and BleepingComputer (endpoints, seven layers) and The Register (the two emails, and the campaign rate as Microsoft stated it to The Register).
Key judgments
- The lure borrows a real vendor relationship. Two near-identical emails spoofed an accounts-payable contact at a contractor and reached a payments contact at a US life-sciences company, with Reply-To pointing to an unrelated domain and SPF, DKIM and DMARC all failing; in AegisAI's assessment, a payments team sees a routine invoice chase.
- The link reads as the vendor's own SharePoint tenant but leads to a lookalike tenant in an attacker-controlled Microsoft 365 workspace. Because the host is still sharepoint.com, the message is less likely to be flagged, as The Register reports.
- ARToken is a full operator environment, not a single page. The exposed interface covers device code phishing, token persistence, mailbox access, business email compromise and SharePoint theft, and one researcher called it "a complete BEC operations environment".
- Operators can escalate a captured token into a Primary Refresh Token that survives a password reset. In AegisAI's assessment, a password reset alone therefore does not end access after a token is taken.
- The platform kept moving. The panel analysed in July was no longer reachable when the first reports ran, and The Hacker News reported on 26 October a campaign built on an updated version that chained a compromised SharePoint tenant, Google Sites and Cloudflare Workers.
How do attackers carry out vendor email compromise with a lookalike SharePoint tenant?
Vendor email compromise is usually described as a hijacked or impersonated supplier account sending a fraudulent invoice or a bank change. ARToken adds a second step. The invoice email is the delivery vehicle for a sign-in, not only for a payment request.
The Register reports that researchers recovered two near-identical emails on 20 April 2026. They used an outstanding-invoice lure ("the following invoices appear to still be outstanding") and exploited a real relationship between a US life-sciences company and a plumbing and fire-protection contractor. Help Net Security adds that the sender spoofed an accounts-payable contact at a Wisconsin contractor and the recipient was a payments contact at the life-sciences company.
- The operator spoofs an accounts-payable contact at a vendor the recipient already pays.
- The From line carries the vendor's real domain; replies are redirected through Reply-To to an unrelated domain.
- The email asks about invoices that "appear to still be outstanding".
- The visible link text reads as the vendor's SharePoint tenant; the real link goes to a near-identical lookalike tenant.
- The recipient is taken to a device code sign-in on Microsoft's own page.
What the email gives away, and what it hides
Help Net Security reports that SPF, DKIM and DMARC all failed on the message, and that each copy carried short random text and an inline signature image. In AegisAI's assessment, the random text is consistent with light per-message variation meant to defeat exact-match filters; the reporting does not state its purpose.
The link is the stronger disguise. The Register describes the destination as a near-identical copycat of the vendor's tenant inside an attacker-controlled Microsoft 365 workspace. Because the host is still sharepoint.com, the email is less likely to be flagged. A reader checking the link text sees the vendor; the real address is still a SharePoint address.
The sign-in page is Microsoft's own, the host is a real SharePoint domain, and the sender is a vendor the recipient knows. Each familiar part is real; the combination is the attack.
AegisAI Threat IntelligenceWhat is ARToken and how is it related to EvilTokens?
ARToken is a phishing-as-a-service operator panel, titled "ARToken Panel" and built as a React web application. Help Net Security reports that researchers found it during an incident response engagement and that it exposes more than eighty endpoints covering device code phishing, token persistence, mailbox access, business email compromise and SharePoint theft.
BleepingComputer reports that the platform "appears to operate as an affiliate of the EvilTokens phishing platform". It uses an identical POST /api/device/start call to start the device code flow, the same Primary Refresh Token endpoints (setup, refresh, renewal and reacquisition) and a similar Cloudflare Workers deployment model. The Register adds that the API contract matches the one first documented for EvilTokens, and that ARToken appears to be an EvilTokens customer. A researcher quoted by Help Net Security said it "does appear to be more of an affiliate's customized build than anything else".
How big is EvilTokens?
Help Net Security describes EvilTokens as a subscription phishing service that spread across hundreds of Cloudflare Workers domains and runs an AI-assisted business email compromise pipeline in its second stage. It was first documented in March 2026. The Register reports that a Microsoft vice president of security research said: "Since March 15, 2026, we have observed 10 to 15 distinct campaigns launching every 24 hours." Each campaign targets hundreds of organizations with varied payloads. BleepingComputer, citing Push Security, reports that device code phishing attacks rose 37-fold over the past year.
What device code phishing abuses
The OAuth 2.0 Device Authorization Grant (RFC 8628) is a sign-in flow built for devices without a keyboard. BleepingComputer reports that victims enter a legitimate Microsoft-issued code on Microsoft's real sign-in page, and Microsoft then issues the tokens to the attacker. Authentication happens on Microsoft's infrastructure, so MFA can be bypassed. For a different device code kit with a different delivery method, see AegisAI's Wazza analysis.
What the operator gets after a token is captured
BleepingComputer reports that the panel goes well beyond a phishing page. Reverse engineering of its client-side JavaScript showed these capabilities:
- Stealing Microsoft 365 tokens and keeping access through Primary Refresh Tokens (PRTs).
- Access to Outlook, SharePoint and OneDrive, including sending mail as the victim and downloading attachments.
- Inbox rules that forward mail, or hide or delete it.
- Keyword monitoring across multiple compromised mailboxes, and loading tokens from other sources.
- A multi-tenant design in which affiliates manage campaigns in dedicated workspaces, with phishing pages that can change content by the victim's location.
Help Net Security adds that operators can escalate tokens into PRTs that survive password resets, and that a companion Windows tool opens a victim's Microsoft 365 session outside the panel. The Register quotes the researcher's conclusion: "it is a complete BEC operations environment."
How does the seven-layer anti-bot check keep scanners away from the lure?
Help Net Security reports that the phishing page runs seven layers of checks before it serves the device code lure. It describes two groups. Early checks read browser traits to screen out headless browsers, automation tools and crawlers. Later checks hold the payload back until mouse movement or a screen touch is detected and a short delay after page load has passed. The payload is scrambled and unpacks only in the browser.
The Register reports that researchers found the evasion capabilities "notably more sophisticated" than what had been seen from EvilTokens. In AegisAI's assessment, the effect is that an automated scanner is shown an inert page while a person with a mouse is shown the lure. The reporting does not list the individual layers.
Is ARToken still active?
Help Net Security reports that the panel researchers examined was no longer accessible when the first reports ran. A researcher quoted there said no takedown had been coordinated, and that the panel was "likely moved".
The Hacker News reported in its 26 October 2026 weekly recap, citing a security vendor's research, a campaign built on an updated version of ARToken. Spoofed emails urged recipients to review a request for proposal document or a payment invoice. The link led to a compromised SharePoint tenant hosting a .URL file that pointed to content on Google Sites, which then redirected victims to a Cloudflare Workers-hosted URL serving the device code lure. The lure's obfuscated JavaScript included anti-analysis checks designed to detect virtualized and automated browsing environments, a hardcoded URL for the ARToken backend panel and a polling-path variant that differs from the endpoints described in the earlier reporting.
Indicators
| Indicator (defanged) | Type | Reported use |
|---|---|---|
pamconj[.]com | Domain | Named by Help Net Security as the lead domain of the operation; the full list is in the original research |
POST /api/device/start | API call | Starts the device code flow; identical in ARToken and EvilTokens (BleepingComputer) |
the following invoices appear to still be outstanding | Email text | Lure wording in the two 20 April 2026 emails (The Register) |
| Lookalike SharePoint tenant | Pattern | A copy of the vendor's tenant name inside an attacker-controlled workspace, on sharepoint.com |
Historical indicators, not a live blocklist. The panel moved after the first reports, and the October variant uses a different polling path.
Why standard controls miss it
Each layer a defender usually leans on sees something that looks normal.
- Sender checks. The reported emails failed SPF, DKIM and DMARC. That is a signal, but in AegisAI's assessment it only helps where a policy acts on it, and the From line carries the vendor's real domain.
- Link reputation. The destination sits on sharepoint.com, so, as The Register reports, the message is less likely to be flagged.
- Link and page scanning. The anti-bot layers screen out automated visitors, so a scanner that cannot pass them is shown a page without the lure.
- MFA. The code is entered on Microsoft's real sign-in page and the MFA challenge is genuinely completed. The token goes to the operator.
- Password reset. A token escalated to a Primary Refresh Token survives it.
How AegisAI protects against it
The lures in the reporting were emails: two invoice messages in the original sample and request-for-proposal and invoice messages in the later campaign. The approach below applies to both.
Aegis does not classify infrastructure. It classifies intent. A lure with no attacker-owned infrastructure still has to ask the recipient to do something on the attacker's behalf, and that request is what gets classified, independent of how clean the destination URL is.
AegisAI's agents evaluate the message and the destination it points to together, and pull a malicious message out of mailboxes before users see or click it.
When a lure or a compromised session is caught, the response compounds: the message is withheld at classification, copies already delivered are retracted, rewritten links refuse a late visit, the account's outbound and internal mail gets rescanned, and lateral phishing attempts to colleagues are blocked at the same bar rather than treated as a fresh, unrelated message.
More on how that works: inbound email security.
What the reporting does not tell us
Scale. The reporting gives no victim count specific to ARToken. It is unclear how large the affiliate's operation is next to the wider EvilTokens platform.
Delivery. The reporting describes two emails from one engagement. It does not show how many organizations received ARToken lures, or whether the invoice theme is the only one in use.
The anti-bot layers. Help Net Security says there are seven but describes only two groups, so the full list is not in the public reporting reviewed here.
The October campaign. The Hacker News item is a recap entry citing one vendor's research. It does not give a victim count, a date for the activity or the lure recipients.
Indicators. The panel moved after the first reports and the later variant uses different polling paths, so published hostnames should be treated as aged.
MITRE ATT&CK mapping
| ID | Name | Use in this campaign |
|---|---|---|
T1566.002 | Phishing: Spearphishing Link | An invoice email carries a link that reads as the vendor's SharePoint tenant but leads to a lookalike tenant. |
T1656 | Impersonation | The sender spoofs an accounts-payable contact at a real vendor. |
T1528 | Steal Application Access Token | The device code flow ends with Microsoft issuing tokens to the operator. |
T1497.001 | Virtualization/Sandbox Evasion: System Checks | Browser-trait and input checks screen out automated visitors before the lure is served. |
T1114.002 | Email Collection: Remote Email Collection | The panel reads victim mailboxes and downloads attachments. |
T1114.003 | Email Collection: Email Forwarding Rule | Inbox rules forward, hide or delete mail. |
Mapping by AegisAI from the behavior described in the reporting. The reporting itself does not publish ATT&CK IDs.
Recommendations for defenders
- Block device code flow where it is not needed. Microsoft Learn recommends getting as close as possible to a unilateral block with a Conditional Access policy, starting in report-only mode and auditing existing use first. Allow it only for documented, secured cases such as legacy tooling that cannot be updated.
- Act on failed authentication for vendor mail. Quarantine or hold external messages that fail SPF, DKIM and DMARC and carry invoice or payment wording, and flag a Reply-To domain that differs from the From domain.
- Check where a link really goes. Compare the visible link text with the real destination, and treat a SharePoint tenant name that differs from the vendor's known tenant as a hunting lead.
- Verify payment conversations out of band. Require a callback to a number held on file for invoice follow-ups and any change of payment details, whatever the email says.
- After a suspected token theft, revoke more than the password. Revoke sessions and tokens, review registered devices, and audit mailbox rules that forward or hide mail, because a Primary Refresh Token survives a password reset.
FAQ
What is vendor email compromise and how do attackers carry it out?
Vendor email compromise is fraud in which an attacker impersonates or takes over a supplier's email to deceive that supplier's customers. In the ARToken campaign the sender was spoofed rather than taken over: an invoice-chase email from a real vendor domain, with Reply-To pointing elsewhere and a link to a lookalike SharePoint tenant that led to a device code sign-in.
What is ARToken and how is it related to EvilTokens?
ARToken is a phishing-as-a-service operator panel with more than 80 API endpoints for device code phishing, token persistence, mailbox access and business email compromise. BleepingComputer reports that it appears to operate as an affiliate of EvilTokens, with the same device code API call, the same Primary Refresh Token endpoints and a similar Cloudflare Workers deployment model.
How does device code phishing bypass MFA?
The attacker starts a Microsoft device code sign-in and persuades the victim to enter the code on Microsoft's real page. The victim completes the password and MFA step for real, and Microsoft issues the tokens to the attacker's session. MFA has already succeeded by the time the attacker holds the token.
Is ARToken still active?
The panel analysed in July was no longer accessible when the first reports ran, and a researcher said it had likely moved. The Hacker News reported on 26 October 2026 a campaign built on an updated version of ARToken that routed victims through a compromised SharePoint tenant and Google Sites to a Cloudflare Workers-hosted device code lure.
References
- The Register (1 Jul 2026). EvilTokens device-code phishing kit totally more evil than we all thought. theregister.com
- Help Net Security (1 Jul 2026). The ARToken phishing panel targets Microsoft 365 accounts. helpnetsecurity.com
- BleepingComputer (3 Jul 2026). ARToken PhaaS exposes EvilTokens' Microsoft 365 phishing toolkit. bleepingcomputer.com
- The Hacker News (26 Oct 2026). Weekly Recap: This2Shell, That2Shell, Everything's an RCE? Rogue AI, Supply Chain Chaos and More. thehackernews.com
- IETF. RFC 8628, OAuth 2.0 Device Authorization Grant. datatracker.ietf.org
- MITRE ATT&CK. T1566.002, T1656, T1528, T1497.001, T1114.002, T1114.003. attack.mitre.org
- Microsoft Learn (updated 7 Apr 2026). Block authentication flows with Conditional Access policy. learn.microsoft.com
Every email, investigated.
Related posts
More from the AegisAI blog.
