Which versions of spectral-corsair-my-backdoor are malicious?

The following npm versions of spectral-corsair-my-backdoor are flagged malicious: 99.99.101. Treat any of these as compromised.

How do I remediate spectral-corsair-my-backdoor if I installed it?

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

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

Yes — spectral-corsair-my-backdoor is associated with the GHSA-j5w6-gpq8-mpf4, RLMA-2026-01815, RLUA-2026-02043 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-corsair-my-backdoor 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 spectral-corsair-my-backdoor (version 99.99.101). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spectral-corsair-my-backdoor across your stack and pipelines.

Malicious package

spectral-corsair-my-backdoornpm

Malicious code in spectral-corsair-my-backdoor (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1374

Immediate action

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

npm uninstall spectral-corsair-my-backdoor

What this malware does

Malicious package detected. Suspicious preinstall script exfiltrates data to a remote server. Multiple YARA rules and LLM analysis confirm.

The package spectral-corsair-my-backdoor was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

99.99.101

Indicators of compromise (SHA-256)

267e29cf3b09a13657871b34148c0a4bb4835071d299dbbc9beb9c3a34ab79b2

0826a28f7948e68cdddd6260a01c3653a7f04deb2c9368054243ed47713ee353

810dd62376efae8ed4d7930ca933bc5eee8eeabf3af7a6124f57c003c136611c

d060ced2004d242b3e5d85542caca5b1c0f721c728bef8b0fb58b52e5181b1d5

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for spectral-corsair-my-backdoor (version 99.99.101). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spectral-corsair-my-backdoor across your stack and pipelines.
If you installed it — respond
spectral-corsair-my-backdoor 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 spectral-corsair-my-backdoor 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 spectral-corsair-my-backdoor 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. spectral-corsair-my-backdoor on npm has been identified as a malicious package (version 99.99.101 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j5w6-gpq8-mpf4RLMA-2026-01815RLUA-2026-02043

References

Credits

Amazon Inspector · finder
ReversingLabs · finder
SafeDep · finder

Detect & block this

O3 blocks spectral-corsair-my-backdoor-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