Which versions of cornerstone_ui_core are malicious?

The following npm versions of cornerstone_ui_core are flagged malicious: 99.9.0. Treat any of these as compromised.

How do I remediate cornerstone_ui_core if I installed it?

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

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

Yes — cornerstone_ui_core is associated with the GHSA-65pp-36gg-69xc, RLMA-2025-04976, RLUA-2026-01225 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 cornerstone_ui_core 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 cornerstone_ui_core (version 99.9.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cornerstone_ui_core across your stack and pipelines.

Malicious package

cornerstone_ui_corenpm

cornerstone_ui_core is a confirmed malicious npm package (MAL-2025-47055) that executes malicious code on install (malicious version 99.9.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cornerstone_ui_core (npm)

MAL-2025-47055

Immediate action

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

npm uninstall cornerstone_ui_core

What this malware does

The package cornerstone_ui_core 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

1 flagged

99.9.0

Indicators of compromise (SHA-256)

76275d4480426c8c60d2ef0233c3df0f042494623872c889c0e28d2212b949fe

586f7efef058d6ceba54f37acac09bb5f404fcb3cd1bce4837b210cb39f35087

73772b730f270118764c8ca9cc6c4f88caa7ca8bf704f52856b9e38e4072d9ea

df4f1a7bc8e3b7ff08599a2a8c58f078d02aa28e588b066cda40d75d32a6a235

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

Campaign

GHSA-65pp-36gg-69xcRLMA-2025-04976RLUA-2026-01225

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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