npm

The @apexacc/cli npm Supply Chain Attack

Updated 21 Oct 2026 · Incident date 17 Sept 2026

@apexacc/cli 1.5.122 on npm turned off Windows Defender and Smart App Control, then ran a program taking remote orders, on 17 September 2026.

The package is sold as an AI advisor for startup founders. Version 1.5.121 ran the same two commands in plain code, and they usually failed for lack of rights.

What happened

Version 1.5.122 encodes two commands in base64 and runs them in a hidden PowerShell window with administrator rights.

  • The first command adds a Defender exclusion for the .apex folder in the user\'s home directory.
  • The second command sets a registry value under HKLM\SYSTEM\CurrentControlSet\Control\CI\Policy that turns off Smart App Control.
  • The tool downloads a Windows file of 110,948,352 bytes from the project\'s own GitHub releases.
  • That file sends a POST request to https://vrf.apexaccs.org/api/v1/vrf with the body {"p":"win32"}.
  • It writes the reply to %TEMP%\_apex_run.ps1 and a launcher to %TEMP%\_apex_run.vbs, then runs the launcher detached.

Version 1.5.122 went live on 17 September 2026 at 08:27 UTC, after 1.5.120 at 08:19:39 and 1.5.121 at 08:26:10.

Vigilance found the release on 17 September 2026, eleven hours after it went to npm. No advisory for this package existed then. Vigilance published it as advisory VIGI-001-2026.

Affected versions

  • @apexacc/cli 1.5.122 and later releases carry the hidden elevation code.
  • @apexacc/cli 1.5.121 runs the same two commands in plain code with no request for administrator rights.
  • The attack targets Windows 11.
  • The macOS build ships a helper named apex-verify-darwin that contains the same vrf.apexaccs.org address.

Indicators of compromise

  • Primary server: https://vrf.apexaccs.org/api/v1/vrf.
  • Second server: https://arena.apexaccs.org/api/copilot/* and https://arena.apexaccs.org/api/llm/v1.
  • Domain: apexaccs.org. Namecheap registered it on 8 August 2026. It is one letter longer than the package's own apexacc name.
  • Files dropped: %TEMP%\_apex_run.ps1, %TEMP%\_apex_run.vbs, ~/.apex/apex-token and ~/.apex/.key.
  • Windows binary SHA-256: cc0910a655335297747d06772f3b4aedd92d0f3c0646cb8af585266521129a50.
  • macOS helper SHA-256: b0cb369029a7dd7de6510d60caac154a0bd91ad6b9a08d69c90227627743ec71.
  • Package tarball 1.5.122 SHA-256: 7c43726fcfdf5393854f34886c02ae63d82cc057ae6ab0e7bf05d0b1b9966725.
  • Accounts: npm apexaccelerator, GitHub apexfdn.
  • A Defender exclusion for the .apex folder, and Smart App Control turned off without your action.

How to check

Look for the package in your projects and global installs.

npm ls -g @apexacc/cli
npm ls @apexacc/cli

On Windows, look for the folder, the dropped script and the Defender exclusions.

Test-Path "$env:USERPROFILE\.apex"
Test-Path "$env:TEMP\_apex_run.ps1"
(Get-MpPreference).ExclusionPath

What to do now

If you ran @apexacc/cli on Windows 11 after 17 September 2026, treat the machine as exposed.

  1. Uninstall the package and delete the .apex folder (%USERPROFILE%\.apex on Windows, ~/.apex on macOS).
  2. Turn Smart App Control back on in Windows Security, and remove the Defender exclusion for that folder.
  3. Rotate credentials from a machine you trust, including npm tokens, SSH keys, browser passwords, wallets, CI and cloud secrets. Revoke any API key you entered in the tool.
  4. Block apexaccs.org at your DNS or proxy.

What Vigilance would show

These examples show an install hold and the corresponding owner report.

Example install message

Vigilance blocked `@apexacc/cli` 1.5.122. This version is too new or changed in a way Vigilance must check first.

Example owner report

Bad update

@apexacc/cli 1.5.122

A founder's AI assistant gained the ability to turn off Windows Defender and Smart App Control from a hidden administrator window, then take orders from a server.

See what to do now.

No security team? See who reads the alert.

Frequently asked questions

Did anyone review the change?

The repository shows eight commits on the main branch that day, all titled "minor fix". It has no pull requests.

What else goes to the attacker's domain?

The same binary sends its AI-copilot traffic to arena.apexaccs.org/api/llm/v1. An API key that a user enters for those features goes through that server.

Who registered the domain?

Namecheap registered apexaccs.org on 8 August 2026. It is one letter longer than the package's apexacc name.

Sources

  1. vigihq.com/reports/vigi-001-2026

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · npm supply chain attacks · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library