Which versions of sensay-cli are malicious?

The following npm versions of sensay-cli are flagged malicious: 2.0.0, 2.0.1. Treat any of these as compromised.

How do I remediate sensay-cli if I installed it?

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

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

Yes — sensay-cli is associated with the GHSA-v295-wm37-56m3, RLMA-2025-05151, RLUA-2026-01556 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 sensay-cli 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 sensay-cli (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sensay-cli across your stack and pipelines.

Malicious package

sensay-clinpm

sensay-cli is a confirmed malicious npm package (MAL-2025-47348) that executes malicious code on install (malicious versions 2.0.0, 2.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sensay-cli (npm)

MAL-2025-47348

Immediate action

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

npm uninstall sensay-cli

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

2 flagged

2.0.02.0.1

Indicators of compromise (SHA-256)

7cb7ee6c9001f05dabc23897e95ab73cf8e80b296c65d848d3d31fa9b2b592ec

dceafa8c5b013882ce9aeb6a21c8e688990f0c72bc07eb2efc98aa965a1dcdc5

1aa51eb7ac63acbe0d8d8fcb7f06d53f5007b56a3da857e05a4d53c8e9f6dd79

a812cbbed6cf372feebb9f0cbf75728704f7f027d858f4320455306bd05d207d

bf9f4e6695a3a7d7b45c78716d0eb16189e007574c248d0c7c881ce13c11cad7

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

Campaign

GHSA-v295-wm37-56m3RLMA-2025-05151RLUA-2026-01556

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks sensay-cli-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