NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

aclade-agentnpm

Advisory published Updated

aclade-agent is a confirmed malicious npm package (MAL-2026-13614) that executes malicious code on install (malicious versions 1.0.1, 1.0.2, 1.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aclade-agent (npm)

MAL-2026-13614
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall aclade-agent

What this malware does

The package runs as a daemon that polls https://aclade.com/api/connector/poll and executes task objects returned by the remote server. Supported operations include execute_bash (child_process.spawn with shell:true on a server-supplied command string), read_file/write_file/replace_file_content against arbitrary filesystem paths, recursive directory listing, grep_search, and schedule_cron (cron.schedule wrapping child_process.exec on a server-supplied command, providing persistence across reboots). All task fields come from the network peer, giving aclade.com full remote code execution, filesystem read/write, and scheduled-task persistence on any host running the agent. The daemon additionally polls https://registry.npmjs.org/aclade-agent/latest hourly and, on version change, runs npm install -g aclade-agent@latest and re-execs itself, so any future publication of the package (including from a compromised maintainer account) is automatically fetched and executed at the daemon's privilege level (README documents global install via sudo/PM2).

Malicious versions

5 flagged
1.0.11.0.21.0.41.0.51.0.6

Indicators of compromise (SHA-256)

228b5c0bac20b8667155520d95e946b292167cd04c0fb9bf244d6f66200332ea
46cdbc08753740ec1f23b0cb77a400e67741099c0c8cc743c4a86cb61ec6fd0b
8ef6554961bfa0fd7794f383f3d385cb79bf4ac1af60598343e782142d2e7058
a2b361ca760d6a5ed8413f5b9212bc775b6c321183c15f60fb14973b83fddc3d
d8babf2ddba443878ed2357fc1991d98d268b775a9014ba8ad00d8d753ee4921

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for aclade-agent (5 malicious versions).

  2. If you installed it — respond

    Remove aclade-agent from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If aclade-agent 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. aclade-agent on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.4, 1.0.5, 1.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017116IN-MAL-2026-017117IN-MAL-2026-017118IN-MAL-2026-017115IN-MAL-2026-017119

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks aclade-agent-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

aclade-agent (npm) malicious package — MAL-2026-13614 | O3 Security