EvilAI: fake AI apps steal browser data
Signed, working productivity apps hide browser-data theft and other malicious behavior. Researchers described the code as AI-generated-looking; that does not independently establish AI authorship.
What happened
Operators distribute fake AI/productivity apps (PDF editors, browsers, recipe tools, etc.) with realistic UIs, working features, and code-signing. Steal browser data, fingerprint systems, disable some security tools, AES-encrypted C2. Trend notes AI-generated-looking clean code aiding evasion. Names include App Suite, Epi Browser, JustAskJacky, Tampered Chef, et al.
How it happened
Read the flow as text & sources
A catalog reconstruction of the supplied source account. Unknown steps remain explicit; an edge describes the reported relationship between steps.
- 01 · User installs a productivity app
Realistic AI and productivity applications offer working-looking interfaces.
Hunt: A newly downloaded or staged executable runs from a user-writable location and exhibits the reported follow-on behavior.
Many approved installers run from user-writable folders. These events are hunt candidates, not proof of malware or an enforced block.
MagicSword policy opportunity · Windows payloads when the policy denies their signer or hash. A valid signature alone does not establish that an app is approved.
Source for step 1 - 02 · AI-themed functionality lends credibility
The research also notes code characteristics consistent with AI assistance.
Hunt: An impersonating message, ad or website leads to a suspicious download, consent request, pasted command or payment instruction.
Polished text, AI branding and a novel domain do not prove maliciousness or AI generation. Follow-on evidence matters.
Source for step 2 - 03 · Application performs hidden actions
The installed app fingerprints the host and communicates with encrypted C2.
Hunt: An unexpected process or tool accesses credential stores and is followed by token use or outbound transfer inconsistent with the owner.
Defender DeviceFileEvents is not a general file-read audit trail. Collect suitable object-access, EDR or application logs; legitimate developer tools also read secrets.
Source for step 3 - 04 · Browser data theft
The reported operation steals information and attempts to disable some security tools.
Hunt: An unexpected process or tool accesses credential stores and is followed by token use or outbound transfer inconsistent with the owner.
Defender DeviceFileEvents is not a general file-read audit trail. Collect suitable object-access, EDR or application logs; legitimate developer tools also read secrets.
Source for step 4
Why it matters
Reported entry point: Users install fake AI/productivity apps. Reported impact: The reported operation steals information and attempts to disable some security tools; reported targets include Global organizations (Trend: far-reaching); applicability to your setup has not been assessed, so verify affected versions, permissions, and configuration in the original report.
What you can do
Protection & prevention
Allowlist apps; block unexpected signed-but-unknown publishers; MagicSword default-deny
Catalog defensive guidance based on the reported behavior. Confirm scope and current mitigations in the original source.
Detection queries
Draft query starters grouped by the attack stages where they apply.
Start with the logs you collect. Each hunt identifies its required visibility, field mapping and limits. Queries are catalog-authored drafts using reusable behavior profiles; test with known activity and your normal baseline before alerting.
01User installs a productivity appUnapproved Windows program executionNative logs · Draft
Realistic AI and productivity applications offer working-looking interfaces.
What to look for
A newly downloaded or staged executable runs from a user-writable location and exhibits the reported follow-on behavior.
Visibility: Defender-side logs where collected
Required logs
- Windows process creation
- Download provenance and file hashes
- File certificate information and application-control audit / block events
Coverage limit. Many approved installers run from user-writable folders. These events are hunt candidates, not proof of malware or an enforced block.
Windows process candidates. Sigma uses normalized process_creation fields; KQL requires Defender for Endpoint; SPL requires the Sysmon XML sourcetype. Tune collectors, fields and baselines before use.
Sigma
title: Hunt - Unapproved Windows program execution
id: e217e948-e57c-48b8-a331-66006de42ae1
status: experimental
description: A newly downloaded or staged executable runs from a user-writable
location and exhibits the reported follow-on behavior.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: process_creation
product: windows
detection:
selection:
Image|contains:
- \Downloads\
- \AppData\Local\Temp\
- \AppData\Roaming\
condition: selection
KQL
// Draft hunt; requires Defender for Endpoint process telemetry for this OS.
DeviceProcessEvents
| where Timestamp > ago(7d)
| where FolderPath contains "\\Downloads\\" or FolderPath contains "\\AppData\\Local\\Temp\\" or FolderPath contains "\\AppData\\Roaming\\"
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, SHA1
| order by Timestamp descSPL
sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
Image IN ("*\\Downloads\\*", "*\\AppData\\Local\\Temp\\*", "*\\AppData\\Roaming\\*")
| table _time host User Image CommandLine ParentImage ParentCommandLine
| sort - _timeInvestigation steps
- Verify publisher, hash, origin, prevalence and local approval rather than trusting a product name or signature.
- Trace child processes and related credential, network or persistence events.
02AI-themed functionality lends credibilityLure → user action / deliveryCustom schema · Draft
The research also notes code characteristics consistent with AI assistance.
What to look for
An impersonating message, ad or website leads to a suspicious download, consent request, pasted command or payment instruction.
Review the delivery chain and program provenance. Code style or apparent AI functionality does not establish maliciousness or AI authorship.
Visibility: Defender-side logs where collected
Required logs
- Email / secure-web-gateway records
- Browser redirects, downloads and URL reputation
- User reports and downstream execution / identity events
Coverage limit. Polished text, AI branding and a novel domain do not prove maliciousness or AI generation. Follow-on evidence matters.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Lure → user action / delivery
id: e0056b49-9905-485b-ac12-2aa076a7bc82
status: experimental
description: An impersonating message, ad or website leads to a suspicious
download, consent request, pasted command or payment instruction.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- message.link.click
- web.download
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("message.link.click", "web.download")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("message.link.click", "web.download")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Reconstruct redirect and delivery provenance using original report indicators, without visiting payload URLs.
- Correlate the click with the actual download, consent or execution; verify the sender through an independent channel.
03Application performs hidden actionsSensitive store access → credential useCustom schema · Draft
The installed app fingerprints the host and communicates with encrypted C2.
What to look for
An unexpected process or tool accesses credential stores and is followed by token use or outbound transfer inconsistent with the owner.
Visibility: Defender-side logs where collected
Required logs
- File-read / API access telemetry for relevant secret stores
- Process identity and command lines
- Identity, token and outbound-network audit logs
Coverage limit. Defender DeviceFileEvents is not a general file-read audit trail. Collect suitable object-access, EDR or application logs; legitimate developer tools also read secrets.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Sensitive store access → credential use
id: 46c46c62-2d83-4198-a8bf-d6637094527b
status: experimental
description: An unexpected process or tool accesses credential stores and is
followed by token use or outbound transfer inconsistent with the owner.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- secret.read
- credential.store.read
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("secret.read", "credential.store.read")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("secret.read", "credential.store.read")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Identify the actor, process and exact store touched, then pivot to token use from new devices or infrastructure.
- Correlate reads with egress and rotate affected credentials after confirming exposure.
04Browser data theftSensitive store access → credential useCustom schema · Draft
The reported operation steals information and attempts to disable some security tools.
What to look for
An unexpected process or tool accesses credential stores and is followed by token use or outbound transfer inconsistent with the owner.
Investigate browser-store reads, token use and egress; investigate security-tool changes separately with product-specific logs.
Visibility: Defender-side logs where collected
Required logs
- File-read / API access telemetry for relevant secret stores
- Process identity and command lines
- Identity, token and outbound-network audit logs
Coverage limit. Defender DeviceFileEvents is not a general file-read audit trail. Collect suitable object-access, EDR or application logs; legitimate developer tools also read secrets.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Sensitive store access → credential use
id: 46c46c62-2d83-4198-a8bf-d6637094527b
status: experimental
description: An unexpected process or tool accesses credential stores and is
followed by token use or outbound transfer inconsistent with the owner.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- secret.read
- credential.store.read
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("secret.read", "credential.store.read")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("secret.read", "credential.store.read")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Identify the actor, process and exact store touched, then pivot to token use from new devices or infrastructure.
- Correlate reads with egress and rotate affected credentials after confirming exposure.
Technical detailsTooling, impact
Attack context
- AI's role
- AI tool as lure
- Initial access
- Users install fake AI/productivity apps
Tooling as reported
AI products, models and artifacts
- Fake AI-branded applications
- AI-assisted clean code (Trend assessment)
Other tooling
- AES C2
- code signing abuse
Targets and reported impact
- Targets / sectors
- Global organizations (Trend: far-reaching)
Detection rules
- Review attack-specific indicatorsGUIDANCE
Monitor for the techniques described in EvilAI fake AI/productivity apps with AI-generated code. Refer to sources for specific IOCs and TTPs.
Source defensive notes
Allowlist apps; block unexpected signed-but-unknown publishers; MagicSword default-deny
Sources & research credit
1 sourceResearch by Trend Micro · Trend Micro
Record & downloads
- Source record name
- EvilAI fake AI/productivity apps with AI-generated code
- Entry ID
- evilai-trendmicro-fake-ai-apps-2025
- Catalog review
- October 20, 2026
- Category
- adversary-use-of-ai
- AI involvement confidence
- confirmed