Which versions of notifications-broadcast are malicious?

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

How do I remediate notifications-broadcast if I installed it?

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

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

Yes — notifications-broadcast is associated with the IN-MAL-2026-009854 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 notifications-broadcast 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 notifications-broadcast (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging notifications-broadcast across your stack and pipelines.

Malicious package

notifications-broadcastnpm

Malicious code in notifications-broadcast (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10419

Immediate action

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

npm uninstall notifications-broadcast

What this malware does

[email protected] ships an empty index.js (module.exports = {};) with placeholder metadata (empty description, empty author, version 99.9.1 consistent with a dependency-confusion stub). Its only functional content is a dependency entry that resolves ltidisafe to a tarball URL at https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.3.4.tgz rather than the npm registry. The Google Cloud Storage bucket ltidi.storage.googleapis.com is not tied to a verifiable npm publisher identity, the tarball is not pinned by hash, and the bucket path segment depenconf matches the dependency-confusion attack shape. On npm install, npm fetches this tarball and installs its contents into the installer's node_modules, executing any lifecycle scripts and making its code reachable via require(). Whoever controls the GCS bucket therefore obtains code execution in the installer's environment via the transitive dependency, and the bucket contents can be mutated at any time without any change to this package.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

bd1aba4582464347961d36f63f501a5aaf2c190322e7ab8d8e4231c076b817e2

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 notifications-broadcast (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging notifications-broadcast across your stack and pipelines.
If you installed it — respond
Remove notifications-broadcast 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 notifications-broadcast 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 notifications-broadcast 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. notifications-broadcast 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.

Campaign

IN-MAL-2026-009854

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks notifications-broadcast-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