Which versions of agent-scheduler are malicious?

The following npm versions of agent-scheduler are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate agent-scheduler if I installed it?

Remove agent-scheduler 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.

I already installed agent-scheduler — how do I know if it already compromised me?

If agent-scheduler 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.

Is agent-scheduler part of a known attack campaign?

Yes — agent-scheduler is associated with the RLMA-2026-01882 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find agent-scheduler across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for agent-scheduler (version 0.0.1).

Malicious package

agent-schedulernpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

agent-scheduler is a confirmed malicious npm package (MAL-2026-2726) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in agent-scheduler (npm)

MAL-2026-2726

Immediate action

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

npm uninstall agent-scheduler

What this malware does

The package agent-scheduler was found to contain malicious code.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c045596adec27c992f034fe68b6bcfcd65ab5787358da46d3e3e658107262d0f

8ef725b4f3725bfa9deeef4b7152653c4156fb0feb92d045501c86968bc17525

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for agent-scheduler (version 0.0.1).
If you installed it — respond
Remove agent-scheduler 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.
Did it already run?
If agent-scheduler 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. agent-scheduler on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01882

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks agent-scheduler-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database