What does the sc-announcer malware do?

The OpenSSF Package Analysis project identified 'sc-announcer' @ 99.9.1 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Which versions of sc-announcer are malicious?

The following npm versions of sc-announcer are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate sc-announcer if I installed it?

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

If sc-announcer 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.

How do I find sc-announcer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sc-announcer (version 99.9.1).

Malicious package

sc-announcernpm

Advisory published Oct 20, 2026Updated Oct 20, 2026

sc-announcer is a confirmed malicious npm package (MAL-2026-18064) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sc-announcer (npm)

MAL-2026-18064

Immediate action

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

npm uninstall sc-announcer

What this malware does

The OpenSSF Package Analysis project identified 'sc-announcer' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

38abcbba47f18b6d76a06a770258c620fc322472d0db0d38b67f04805b916d43

Detection & response playbook

Malicious package

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

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks sc-announcer-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