Which versions of xo-tray-height are malicious?

The following npm versions of xo-tray-height are flagged malicious: 99.0.99. Treat any of these as compromised.

How do I remediate xo-tray-height if I installed it?

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

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

Yes — xo-tray-height is associated with the GHSA-q5x3-p23m-9342, RLMA-2025-05202, RLUA-2026-01655 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 xo-tray-height 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 xo-tray-height (version 99.0.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xo-tray-height across your stack and pipelines.

Malicious package

xo-tray-heightnpm

xo-tray-height is a confirmed malicious npm package (MAL-2025-47364) that executes malicious code on install (malicious version 99.0.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xo-tray-height (npm)

MAL-2025-47364

Immediate action

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

npm uninstall xo-tray-height

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

Indicators of compromise (SHA-256)

e77b86db993d991491d3db2d143bb8031f63d03acf7e372dcf716c51987f0d87

a44ffd625df52ae3fa6151a0bf7a2bd979cee87e617aacae3d06197b1f4ba3a6

7ef2c3a768cd19ef8a1fe6491a6305f3d0822af346a1ec60ac0679cc460dee1d

9b9f2d7fdb3966263b2169c8460dcf6e75b451cf6c3c76d6a2551645474d66ef

1d48989b8f22eebfffeb3e9647c21b640edb9be4e87dbfaa520a1c49bf19baf7

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

Campaign

GHSA-q5x3-p23m-9342RLMA-2025-05202RLUA-2026-01655

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks xo-tray-height-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