Fake Web3 Accelerator Apex Distributes Malicious npm Packages to Target Crypto Founders
A deceptive Web3 accelerator named Apex has been distributing malicious npm packages, @apexacc/cli and @apexacc/audit, to steal sensitive data from cryptocurrency founders.

A sophisticated operation masquerading as a legitimate Web3 accelerator, Apex, has been actively targeting cryptocurrency founders and startups by distributing malicious npm packages. These packages, disguised as tools for AI coding assistance and smart-contract auditing, were designed to deliver malware onto victim systems, steal sensitive cryptocurrency-related data, and exfiltrate AI-agent information. The campaign employed advanced social engineering tactics, mimicking legitimate services and events to lure unsuspecting victims into running the compromised code.
The malicious packages, identified as @apexacc/cli and @apexacc/audit, were published by the same entity and presented as part of the "Apex Arena" platform. This platform claimed to offer a suite of services including smart-contract reviews, founder messaging, investment scoring, and AI coding tools like "Apex Copilot." To enhance its credibility, Apex also fabricated positive reviews and advertised participation in real-world industry events like TOKEN2049 in Singapore, a tactic aimed at building trust within the crypto community.
Analysis by Elastic Security Labs revealed that the @apexacc/cli package, intended as an AI coding agent, was largely a copy of the legitimate open-source Oh My Pi coding agent. However, the altered code included a bootstrap component capable of receiving commands from attacker-controlled infrastructure. This allowed the attackers to reroute AI service requests and inject a malicious Model Context Protocol (MCP) server into the victim's configuration, potentially granting them access to sensitive prompts, conversation history, and code snippets.
The malware delivery mechanism was tailored for both Windows and macOS. On Windows, the npm package launchers initiated a multistage infection chain that ultimately deployed a custom information stealer. This stealer was capable of collecting a wide array of sensitive data, including system details, clipboard contents, screenshots, browser credentials, Wi-Fi profiles, and data from cryptocurrency wallets, VPN clients, messaging applications, and other AI clients. The exfiltrated data was then sent to the attackers via Telegram.
For macOS users, a Rust helper component fetched a script that delivered CloudSyncD, a backdoor. This backdoor would prompt the user for administrator credentials through a deceptive pop-up, mimicking legitimate system updates or installations. Once granted, it collected host information and established a command-and-control connection. This delivery method bears similarities to previous campaigns that used counterfeit installers to deploy privileged backdoors on macOS devices.
The second malicious package, @apexacc/audit, was presented as a suite of 18 smart-contract security tools. However, investigations found that these tools consistently returned fabricated results, failing to perform any actual security checks. Some results were hard-coded, while others were randomly generated or based on the current date, providing users with false assurances about the security of their smart contracts.
This campaign highlights the evolving threat landscape targeting the cryptocurrency sector. The attackers leveraged a combination of supply-chain attacks via npm, sophisticated social engineering, and the allure of AI-powered tools to compromise developers and founders who often handle highly sensitive assets like wallet keys and proprietary code on their development systems.
Security researchers advise organizations and individuals to immediately remove the identified Apex packages from developer systems. Furthermore, it is crucial to review shell history and endpoint telemetry for signs of compromise, rotate any exposed secrets including wallet credentials, API keys, and cloud tokens, and examine AI-agent configurations for unauthorized MCP entries. Vigilance in verifying the authenticity and behavior of npm packages before installation remains a critical defense.