Which versions of ashcare-ui-ember are malicious?

The following npm versions of ashcare-ui-ember are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate ashcare-ui-ember if I installed it?

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

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

Yes — ashcare-ui-ember is associated with the RLMA-2026-04946, RLUA-2026-06072 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 ashcare-ui-ember across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ashcare-ui-ember (version 99.99.99).

Malicious package

ashcare-ui-embernpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

ashcare-ui-ember is a confirmed malicious npm package (MAL-2026-7211) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ashcare-ui-ember (npm)

MAL-2026-7211

Immediate action

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

npm uninstall ashcare-ui-ember

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

ed970059e1ff75d4f09136c7297f79be7cabd03c94e7936e39ea0f59e8978a1a

28150a9484354f2ba5ba58da2f732db744e16c26f6fe821534e3ebb3a09f8d6c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04946RLUA-2026-06072

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks ashcare-ui-ember-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