Which versions of spectral-engine are malicious?

The following npm versions of spectral-engine are flagged malicious: 2.14.801. Treat any of these as compromised.

How do I remediate spectral-engine if I installed it?

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

If spectral-engine 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 spectral-engine part of a known attack campaign?

Yes — spectral-engine is associated with the RLMA-2026-01816 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 spectral-engine across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for spectral-engine (version 2.14.801).

Malicious package

spectral-enginenpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

spectral-engine is a confirmed malicious npm package (MAL-2026-2388) that executes malicious code on install (malicious version 2.14.801). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in spectral-engine (npm)

MAL-2026-2388

Immediate action

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

npm uninstall spectral-engine

What this malware does

The package spectral-engine was found to contain malicious code.

Malicious versions

1 flagged

2.14.801

Indicators of compromise (SHA-256)

36c1776e0c796ae4f47d6e682de1e0e487bb462f0768e5023fd00ec90566ec4e

6d45c9e6ca6d123deeb7d3bfb326dc818f76fb83f256dca70e650842b7cf7620

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01816

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks spectral-engine-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