Which versions of ember-livereload-indicator are malicious?

The following npm versions of ember-livereload-indicator are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate ember-livereload-indicator if I installed it?

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

If ember-livereload-indicator 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 ember-livereload-indicator part of a known attack campaign?

Yes — ember-livereload-indicator is associated with the GHSA-wg88-7c9q-pgp8, RLMA-2026-06210, RLUA-2026-10719 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 ember-livereload-indicator across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ember-livereload-indicator (version 99.0.0).

Malicious package

ember-livereload-indicatornpm

Advisory published Jul 30, 2026Updated Sep 24, 2026

ember-livereload-indicator is a confirmed malicious npm package (MAL-2026-11291) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ember-livereload-indicator (npm)

MAL-2026-11291

Immediate action

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

npm uninstall ember-livereload-indicator

What this malware does

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.0.0

Indicators of compromise (SHA-256)

205eabc38fa6c38df3ea030cae6621b16235960c048a8eba382c821863c91da1

c5f20a083bf17aa41bcf7b5ec733e5c5bd5aefc8fecc35f4d815c04b9b72c2c2

a79df1d93d3f6ba23f7e8a3ee73dca2b6b31e40e3892f7129230d1da47a0c9f2

Detection & response playbook

Malicious package

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

Campaign

GHSA-wg88-7c9q-pgp8RLMA-2026-06210RLUA-2026-10719

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks ember-livereload-indicator-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