· Cybersecurity news

Cybersecurity News Today: Fake VC Lured Founders with Free AI, Shipped npm Malware

The cybersecurity news today carries a warning every crypto founder and AI builder should read twice. On October 12, 2026, Elastic Security Labs researchers Jia Yu Chan and Daniel Stepanic unmasked "Apex Accelerator" — a fake Web3 venture-capital accelerator (tracked as REF8801) that courted crypto startups with investment offers, free AI credits, and smart-contract audits, then delivered malware through two npm packages. The devious part: one package was a near-perfect copy of a legitimate open-source coding agent — 1,351 of 1,363 files identical — with a hidden redirect funneling the victim's AI conversations to the attackers.

What is the Apex Accelerator story in today's cybersecurity news?

Apex Accelerator posed as a Web3 VC accelerator, claiming 200+ portfolio projects and $124M+ raised. Its lures were tailor-made for crypto founders:

2malicious npm packages
1,351/1,363files matching legit Oh My Pi agent
18"security tools" — all fabricated findings
51/100score given to a fictitious project

The malicious packages — published by npm user apexaccelerator and linked to GitHub accounts "apexaccs" / "Apex Foundation" — were @apexacc/cli and @apexacc/audit.

How did the fake CLI hijack AI agent traffic?

@apexacc/cli was marketed as "Apex Copilot CLI — AI advisor for Web3 founders," claiming Claude Fable 5 and Gemini 2.5 Flash. In reality it repackaged the legitimate open-source Oh My Pi coding agent — 1,351 of 1,363 files matched upstream exactly. The added bootstrap did two things:

This is the new face of supply-chain attack: not a backdoor in a library, but a parasite on your AI agent's brain — every question you ask the model, every snippet you paste, routed through the attacker.

What was the "security scanner" that lied?

@apexacc/audit claimed to be a "Web3 Security Scanner" with 18 security tools, delivered as an MCP server for tokens, wallets, and smart contracts. All 18 tools returned fabricated findings. Its remote scorer gave 51/100 to a fictitious project while claiming its AI scorer was unavailable. An audit tool that lies is worse than no audit at all — it manufactures false confidence.

What did the malware steal?

A real near-miss: founder @hialex_sol posted on September 14, 2026 that "Apex Accelerator" asked them to run npx @apexacc/cli — it "dropped a hidden, encrypted malware loader disguised as an Apple app. We caught it and lost nothing."

Honest scope: both packages have been removed from npm and the linked repos are now inaccessible — the threat is neutralized for new installs, but anyone who ran these packages may be compromised. Elastic observed no additional macOS payloads delivered during analysis, and the Windows loader had a packaging error in testing. An earlier wave from the same operation (late July 2026) distributed the Atomic Stealer (AMOS) for macOS via @apexfdn/apex, per SafeDep.

How do you spot the next fake accelerator?

Read install scripts. Verify the publisher. Never run unknown npm packages where your crypto or your AI tool configs live.

Sources: Elastic Security Labs ("Auditing the auditor: Unmasking Apex Accelerator," Oct 12, 2026), The Hacker News, GBHackers, cryptika.com.

BreachHunter — Ingenious AI's breach and supply-chain threat platform — is built for exactly this threat model: catching malicious packages before they reach your machine. Get early access on WhatsApp.

Quiz: would YOU have run npx @apexacc/cli?

1. Which npm packages did the fake Apex Accelerator distribute?

2. What did @apexacc/cli repackage?

3. What did @apexacc/audit's 18 "security tools" return?

4. What did the tampered CLI do with OpenRouter-labelled model traffic?

5. What's the #1 red flag of a fake accelerator?

FAQs

What is the Apex Accelerator npm malware campaign?

Apex Accelerator was a fake Web3 venture-capital accelerator (tracked as REF8801) that targeted crypto founders with investment offers, free AI credits (Claude, Gemini), coding tools, smart-contract audits, and event invitations. Its npm packages @apexacc/cli and @apexacc/audit installed a Windows information stealer and a macOS backdoor. Elastic Security Labs researchers Jia Yu Chan and Daniel Stepanic published the findings on October 12, 2026, and both packages have since been removed from npm.

What did the @apexacc/cli package do?

@apexacc/cli, marketed as "Apex Copilot CLI — an AI advisor for Web3 founders" claiming Claude Fable 5 and Gemini 2.5 Flash, repackaged the legitimate open-source Oh My Pi coding agent: 1,351 of 1,363 files matched the upstream project exactly. It added a bootstrap that redirected OpenRouter-labelled model traffic through attacker infrastructure — exposing prompts, conversation history, code snippets, and tool outputs — and persistently registered an attacker-controlled MCP server, giving the attackers a control surface over the victim's AI agent.

What was wrong with the @apexacc/audit security scanner?

@apexacc/audit, marketed as a "Web3 Security Scanner" with 18 security tools, returned fabricated findings for all 18 tools. Its remote scorer gave a score of 51/100 to a fictitious project while claiming its AI scorer was unavailable. It was an audit tool that lied — the opposite of what it claimed to be.

What data did the Apex Accelerator malware steal?

The Windows information stealer collected browser passwords, session cookies, crypto wallets, clipboard contents, screenshots, local files, and even the victim's Claude, Cursor, and Windsurf configurations, exfiltrating everything via Telegram. The macOS CloudSyncD backdoor's installer asked for the administrator password, validated it, and stored it locally.

How can I spot a fake accelerator or malicious npm package?

Red flags from this campaign: unsolicited investment offers paired with "free" tools, pressure to run "npx" on an unfamiliar package, claims that can't be verified (200+ portfolio projects, $124M raised), and packages with little download history or fresh publisher accounts. Verify the publisher, check the repo history, read the install scripts, and never run npm packages from unknown sources on a machine holding crypto wallets or AI tool credentials.