How do I remediate sentinelone if I installed it?

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

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

Yes — sentinelone is associated with the RLMA-2024-04788 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 sentinelone across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sentinelone (21 malicious versions).

Malicious package

sentinelonePyPI

sentinelone is a confirmed malicious PyPI package (MAL-2024-5987) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sentinelone (PyPI)

MAL-2024-5987

Immediate action

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

pip uninstall sentinelone

Malicious versions

21 flagged

1.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.81.0.91.1.01.1.21.1.31.1.41.1.51.1.61.1.71.1.81.1.91.2.01.2.1

Indicators of compromise (SHA-256)

4740c987ac8e9e677f32ea518a079c998ac04865460b6a96eb5e10aa8438388e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sentinelone (21 malicious versions).
If you installed it — respond
Remove sentinelone 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 sentinelone 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. sentinelone on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, and 13 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04788

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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