Which versions of ecosystem_ui are malicious?

The following npm versions of ecosystem_ui are flagged malicious: 10.0.1, 11.0.0, 90.9.9, 99.9.8, 99.9.9. Treat any of these as compromised.

How do I remediate ecosystem_ui if I installed it?

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

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

Yes — ecosystem_ui is associated with the GHSA-rfm3-w7v3-89mx, RLMA-2026-01269 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 ecosystem_ui 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 ecosystem_ui (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ecosystem_ui across your stack and pipelines.

Malicious package

ecosystem_uinpm

Malicious code in ecosystem_ui (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-883

Immediate action

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

npm uninstall ecosystem_ui

What this malware does

The package ecosystem_ui was found to contain malicious code.

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

5 flagged

10.0.111.0.090.9.999.9.899.9.9

Indicators of compromise (SHA-256)

31a22a7e3ce76544adef6885be748f17910483d02a1f19395a520b918516ea63

4987a955f090814c8e125cdaca051b7d106fc4e853cc4e45bc253fbb444f8d94

cde404ceec373c8a0a2e052d2bc23157b7904c2a7993b4b0924bf10c181992b9

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 ecosystem_ui (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ecosystem_ui across your stack and pipelines.
If you installed it — respond
Remove ecosystem_ui 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 ecosystem_ui 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 ecosystem_ui 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. ecosystem_ui on npm has been identified as a malicious package (versions 10.0.1, 11.0.0, 90.9.9, 99.9.8, 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rfm3-w7v3-89mxRLMA-2026-01269

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ecosystem_ui-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