# Apex Accelerator / REF8801

- ID: apex-accelerator-ref8801-2026-10
- Reported: 2026-10-12
- Researcher: Jia Yu Chan, Daniel Stepanic
- Organization: Elastic Security Labs
- AI role: ai_tool_as_lure (AI tool as lure)
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: 2026-10-20
- Entry page: https://openattacks.ai/attacks/apex-accelerator-ref8801-2026-10/
- Entry JSON: https://openattacks.ai/api/attacks/apex-accelerator-ref8801-2026-10.json
- Browse title: Apex Accelerator / REF8801 backdoored AI CLI and MCP packages
- Editorial summary: A fake Web3 accelerator's npm packages route AI traffic to an attacker proxy, register rogue MCP servers in AI IDEs, and drop stealers on Windows and macOS.
- Evidence class (catalog annotation): Reported campaign
- Source-stated target environments: Developer workflows; Agents & MCP; Windows; macOS
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/apex-accelerator-ref8801-2026-10.json

## Technique
Fake Web3 accelerator hands founders free Claude/Gemini credits and npm packages (@apexacc/cli, @apexacc/audit). CLI is Oh My Pi with backdoored bootstrap: OPENROUTER\_BASE\_URL to attacker LLM proxy, rogue MCP in ~/.apex/agent/mcp.json, yolo approvals. Audit MCP returns fabricated findings and registers into Claude Desktop/Cursor/Windsurf. Windows chain: wscript→PowerShell→stealer; macOS CloudSyncD.

## Stack relevance (editorial)
Assessment: mapped. Editorial applicability reviewed against the catalog source account; not a scan or independent incident verification.
First action: Review newly added MCP servers, CLI bootstrap settings and the provenance of accelerator-supplied npm packages.
- Relationship: workflow; tools: cursor, claude, npm-pypi; OS scope: windows, macos; requires existing MCP connections: false.
  Relevance: The campaign registers rogue MCP configurations in AI clients after an attacker-supplied npm bootstrap runs.
  Condition to check: Confirm installation of the accelerator-supplied packages or the rogue configuration; ordinary AI-client use is not the entry point.
  Evidence: https://www.elastic.co/security-labs/threat-command/apex-accelerator-malicious-npm-packages
- Relationship: workflow; tools: no specific product; OS scope: windows, macos; requires existing MCP connections: true.
  Relevance: An untrusted npm bootstrap can add rogue MCP servers and alter agent approval settings.
  Condition to check: The source describes a specific accelerator / npm package lure; check whether those packages or configurations are present.
  Evidence: https://www.elastic.co/security-labs/threat-command/apex-accelerator-malicious-npm-packages
A product mention alone is not a victim-side applicability mapping. Selection does not verify affected versions, permissions or compromise.

## Initial access
Social engineering via fake accelerator / free AI credits; npm install of @apexacc/cli or @apexacc/audit

## AI tooling and models
- [Oh My Pi](https://github.com/can1357/oh-my-pi) (repackaged as Apex Copilot)
- Attacker LLM proxy arena.apexaccs.org/api/llm/v1
- Attacker MCP arena.apexaccs.org/api/copilot/mcp
- Fabricated 18-tool Apex Audit MCP
- Targets [Claude Desktop](https://claude.com/product/overview), [Cursor](https://cursor.com/), Windsurf configs

## Other tooling
- wscript.exe
- [PowerShell](https://github.com/PowerShell/PowerShell)
- [UACME](https://github.com/hfiref0x/UACME) ComputerDefaults bypass
- [Go](https://github.com/golang/go) AMSI/ETW patcher
- CloudSyncD (macOS)
- Telegram exfil
- bludness.exe / exegis.exe

## Victims and sectors
Cryptocurrency / Web3 founders and startups

## Target geography
- Multiple regions
Global Web3 targeting is described. A claimed presence at TOKEN2049 in Singapore is not evidence of a victim in Singapore.

## Attribution
Elastic REF8801; Russian comments in history but nationality not established

## Scale and metrics
unknown

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### step-1: Fake accelerator recruits founders [access]
Free AI credits entice Web3 founders to install npm packages.
Evidence: https://www.elastic.co/security-labs/threat-command/apex-accelerator-malicious-npm-packages

### step-2: Bootstrap changes agent settings [execution]
The packages introduce an attacker LLM proxy, rogue MCP configuration and permissive approvals.
Evidence: https://www.elastic.co/security-labs/threat-command/apex-accelerator-malicious-npm-packages

### step-3: Rogue tools influence the agent [ai]
The audit MCP fabricates findings and registers with desktop coding agents.
Evidence: https://www.elastic.co/security-labs/threat-command/apex-accelerator-malicious-npm-packages

### step-4: Platform-specific malware [impact]
Reported Windows and macOS branches deliver a stealer or CloudSyncD.
Evidence: https://www.elastic.co/security-labs/threat-command/apex-accelerator-malicious-npm-packages

Connections:
- step-1 -> step-2
- step-2 -> step-3
- step-3 -> step-4

## Stage defense and hunting recommendations
Editorial recommendations, not validated coverage. Source-controlled query starters are drafts. Custom-schema examples require telemetry collection and field mapping; absence of a mapping means not assessed. MagicSword policy opportunities require managed Windows scope and enforcement.
### step-1: Lure → user action / delivery
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/phishing.sigma.yml
- KQL query download: /api/detections/phishing.kql
- SPL query download: /api/detections/phishing.spl
- Hunt hypothesis: An impersonating message, ad or website leads to a suspicious download, consent request, pasted command or payment instruction.
- Required telemetry: Email / secure-web-gateway records; Browser redirects, downloads and URL reputation; User reports and downstream execution / identity events
- Investigate: Reconstruct redirect and delivery provenance using original report indicators, without visiting payload URLs.
- Investigate: Correlate the click with the actual download, consent or execution; verify the sender through an independent channel.
- Limitation: Polished text, AI branding and a novel domain do not prove maliciousness or AI generation. Follow-on evidence matters.
- Qualification: Join the accelerator invitation to the package-install request; baseline legitimate recruitment and grants.
- No direct MagicSword prevention claim is recorded for this stage.

### step-2: Agent trust / configuration changes
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/mcp-config.sigma.yml
- KQL query download: /api/detections/mcp-config.kql
- SPL query download: /api/detections/mcp-config.spl
- Hunt hypothesis: A repository, dependency or agent changes MCP commands, automatic-task settings, tool approval or model-routing configuration before new execution.
- Required telemetry: File changes and before/after content for MCP / IDE configuration; Repository audit / pull-request history; Agent startup and tool-invocation logs
- Investigate: Diff command, args, environment, origin, autoApprove and task settings against the previously approved version.
- Investigate: Correlate the author and change with the next agent launch; inspect path canonicalization and trailing-dot variants where relevant.
- Limitation: A file-write event alone cannot establish what changed. Legitimate setup also changes these files; obtain a diff and authorization context.
- No direct MagicSword prevention claim is recorded for this stage.
- Community intelligence: LOLSkills — https://lolskills.io

### step-3: Unexpected agent tool use
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/agent-tools.sigma.yml
- KQL query download: /api/detections/agent-tools.kql
- SPL query download: /api/detections/agent-tools.spl
- Hunt hypothesis: Untrusted content or a changed tool definition precedes a file read, command, or remote call outside the user's intended task.
- Required telemetry: Agent tool-call audit records with session / tool / destination; Tool-definition and approval changes; Endpoint process, file-access and network evidence where available
- Investigate: Join input provenance, tool descriptions and calls by session ID and compare the action to the approved task.
- Investigate: Inspect child processes and destinations; record whether execution was in-process, local, or through a remote SaaS connector.
- Limitation: Process logs cannot recover model intent. Remote connectors and in-process interpreters may produce no local child process. Prompt content alone is not a reliable signature.
- No direct MagicSword prevention claim is recorded for this stage.
- Community intelligence: LOLSkills — https://lolskills.io

### step-4: Suspicious Windows script execution
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: native
- SIGMA query download: /api/detections/windows-shell.sigma.yml
- KQL query download: /api/detections/windows-shell.kql
- SPL query download: /api/detections/windows-shell.spl
- Hunt hypothesis: A script host or shell runs encoded content, a remote URL, or inline script syntax, then downloads or launches a payload.
- Required telemetry: Windows process creation: Sysmon Event 1 or Defender DeviceProcessEvents; PowerShell script-block logging when enabled; Download / network and installer events
- Investigate: Follow the parent and child process tree and recover the script or URL from logs without executing it.
- Investigate: Correlate the payload's signer/hash, persistence, and network activity; baseline approved automation.
- Limitation: Encoded commands and remote administration can be legitimate. This does not cover every script host, in-process execution, or non-Windows branch.
- Conditional MagicSword policy: Use MagicSword to review and enforce a policy restricting unneeded Windows script hosts, shells or installer utilities identified in this branch.
- Policy scope: The Windows wscript → PowerShell branch only. This does not cover the separate macOS CloudSyncD branch.
- Policy limitation: Policy opportunity, not tested incident coverage. Requires enrolled Windows devices, a policy covering the actual executable, and enforcement. Audit mode records decisions without blocking; allowed tools and in-process / cloud actions can remain reachable.
- Policy reference: https://www.magicsword.io/use-cases/application-control?utm_source=openattacks&utm_medium=referral&utm_content=stage-control


## MITRE ATLAS
Mappings are catalog annotations based on described behavior, not assignments or endorsements by MITRE.
- AML.T0081: Modify AI Agent Configuration — The packages rewrite model-proxy and MCP settings.
  Technique: https://atlas.mitre.org/techniques/AML.T0081
  Evidence: https://www.elastic.co/security-labs/threat-command/apex-accelerator-malicious-npm-packages
- AML.T0104: Publish Poisoned AI Agent Tool — The accelerator distributes a rogue audit MCP tool.
  Technique: https://atlas.mitre.org/techniques/AML.T0104
  Evidence: https://www.elastic.co/security-labs/threat-command/apex-accelerator-malicious-npm-packages

## Defensive notes
Block apexaccs.org / apexfdn.xyz / payload domains; audit MCP configs and OPENROUTER\_BASE\_URL; rotate AI keys; prevent wscript (Windows stealer chain depends on it)

## Sources
- https://www.elastic.co/security-labs/threat-command/apex-accelerator-malicious-npm-packages
