Which versions of @apexacc/audit are malicious?

Every published version of @apexacc/audit on npm is considered malicious. Remove the package entirely.

How do I remediate @apexacc/audit if I installed it?

@apexacc/audit is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @apexacc/audit — how do I know if it already compromised me?

If @apexacc/audit was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find @apexacc/audit across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @apexacc/audit (all published versions).

Malicious package

@apexacc/auditnpm

Advisory published Oct 16, 2026Updated Oct 19, 2026

@apexacc/audit is a confirmed malicious npm package (MAL-2026-17923) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @apexacc/audit (npm)

MAL-2026-17923

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @apexacc/audit

What this malware does

@apexacc/audit is the companion package to @apexacc/cli in the "Apex Accelerator" campaign (Elastic Security Labs REF8801, 2026-10-12). It exposes an MCP server with 18 "security tools" that all return fabricated output (for example a fixed Slither report and a "NOT A HONEYPOT" verdict), registers itself in Claude Desktop, Cursor and Windsurf MCP configs, and on Windows requests elevation to add a Defender exclusion for its folder and attempts to disable Smart App Control. It carries the same verification bootstrap as @apexacc/cli (macOS CloudSyncD dropper; Windows staged infostealer). The package returns "Not found" from the npm registry as of 2026-10-15, but installed copies persist. All versions affected. Indicators from Elastic's report.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @apexacc/audit (all published versions).
If you installed it — respond
@apexacc/audit is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @apexacc/audit was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @apexacc/audit on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

elastic.co

Credits

Elastic Security Labs (Jia Yu Chan, Daniel Stepanic) · finder
Patrick Duggan, DugganUSA · reporter

Detect & block this

O3 blocks @apexacc/audit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database