# MAL-2026-18064: Malicious code in sc-announcer (npm)


- **Type:** Malicious package
- **Package:** `sc-announcer` (npm)
- **Published:** 20 Oct 2026
- **Also known as:** GHSA-fxw2-4j5q-6hwg

## What is MAL-2026-18064?

MAL-2026-18064 is a malicious package in sc-announcer, published on 20 Oct 2026. 

### Official description

sc-announcer@99.9.1 ships an empty stub (`module.exports = {}`) and declares a single dependency `ltidisafe` sourced from an off-registry HTTPS tarball URL (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-4.0.2.tgz`) in package.json rather than a registry version range. On `npm install`, npm fetches that tarball and installs whatever bytes it returns, with no version pin, no integrity hash, and no registry provenance; any lifecycle scripts contained inside the fetched tarball execute on the installer's machine. The implausibly high version number (99.9.1) and dependency-confusion-shaped setup — stub package whose only effect is to pull a URL-sourced dependency — are consistent with a resolution-hijack lure targeting an internal package name.

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.

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.

## What should I do about MAL-2026-18064?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-18064 is a malicious package: sc-announcer (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-18064/ (Markdown: https://insights.sbomify.com/MAL-2026-18064/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-18064

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-18064/
Summaries are generated and may contain mistakes; the official description above is the record.