Zimperium says ArcticRAT queried xAI’s Grok API to sort information it had already collected from Android phones. One prompt classified installed financial apps; another sifted harvested text messages for one-time codes, balance changes and transfer alerts. Zimperium published its technical report on November 12, 2026 and says it identified the AI capability in samples analyzed around mid-July 2026.

What ArcticRAT uses Grok to analyze

The reported AI workflow processes data ArcticRAT has already gathered; it does not log in to bank accounts or verify a person’s actual balance. The SMS prompt looks for financial clues in message content, including authentication codes and transfer notices.

In one observed sample, Zimperium identified the model as grok-4.20-0309-non-reasoning. The sample cached its analysis as JSON on the device at /storage/emulated/0/config/AI_DATA/; a command from the malware’s command-and-control system could retrieve those files.

Grok’s reported role is sorting; ArcticRAT’s access to the phone supplies the data.

How ArcticRAT reaches and controls Android devices

Zimperium describes ArcticRAT as a remote-access trojan that evolved from a cryptocurrency-focused stealer targeting users of 11 apps. Reported delivery routes include malicious ads, scam text messages and third-party forums that lead to pages impersonating Google Play. Some payloads were delivered from AWS storage.

The malware’s other reported capabilities include abusing Android Accessibility features, capturing screens, monitoring the microphone, logging keystrokes and using overlays. Zimperium also describes variants that abuse Wireless Debugging and ADB. During staging, a dropper’s VPN service can null-route device traffic, blinding Google Play Protect telemetry during that phase. A simulated extortion screen displays an encryption-style progress bar, but Zimperium says ArcticRAT does not encrypt files.

Precautions for Android users

Infobae reported that Zimperium advised installing apps from the official store, treating requests for Accessibility or VPN permissions during installation with caution, and keeping Wireless Debugging disabled. These precautions address the installation routes and device permissions described in the report.