Which versions of server-authorized-cleanup are malicious?

The following npm versions of server-authorized-cleanup are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate server-authorized-cleanup if I installed it?

Remove server-authorized-cleanup 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 server-authorized-cleanup — how do I know if it already compromised me?

If server-authorized-cleanup was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is server-authorized-cleanup part of a known attack campaign?

Yes — server-authorized-cleanup is associated with the IN-MAL-2026-019850 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 server-authorized-cleanup across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for server-authorized-cleanup (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging server-authorized-cleanup across your stack and pipelines.

Malicious package

server-authorized-cleanupnpm

server-authorized-cleanup is a confirmed malicious npm package (MAL-2026-16079) that executes malicious code on install (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in server-authorized-cleanup (npm)

MAL-2026-16079

Immediate action

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

npm uninstall server-authorized-cleanup

What this malware does

server-authorized-cleanup exposes triggerCleanup() which issues an HTTPS GET to the hardcoded author endpoint https://testback-2aqe.onrender.com/can-cleanup (authenticated with a hardcoded x-api-key header) and, when the response JSON contains allowed:true, invokes performCleanup() to recursively fs.rmSync every entry under the target directory (default process.cwd()). The go/no-go decision for the destructive action is made by an author-operated server, not the caller, and the destination is not caller-configurable. Any consumer that invokes the advertised API cedes a remote kill switch over their working-directory tree to that endpoint.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

ba50dd2c597a65e5fa5bd8aa2675ac16fb443c6d42381921fde160c9596f44d2

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for server-authorized-cleanup (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging server-authorized-cleanup across your stack and pipelines.
If you installed it — respond
Remove server-authorized-cleanup 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 server-authorized-cleanup was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks server-authorized-cleanup before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. server-authorized-cleanup on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019850

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks server-authorized-cleanup-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