Which versions of sentinelone-sdk are malicious?

The following PyPI versions of sentinelone-sdk are flagged malicious: 6.2.1, 6.2.2. Treat any of these as compromised.

How do I remediate sentinelone-sdk if I installed it?

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

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

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

Search your lockfiles and build artifacts for sentinelone-sdk (2 malicious versions).

Malicious package

sentinelone-sdkPyPI

sentinelone-sdk is a confirmed malicious PyPI package (MAL-2024-5988) that executes malicious code on install (malicious versions 6.2.1, 6.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sentinelone-sdk (PyPI)

MAL-2024-5988

Immediate action

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

pip uninstall sentinelone-sdk

Malicious versions

2 flagged

6.2.16.2.2

Indicators of compromise (SHA-256)

8566fa017837b0ef860df52bbd141d14fea45ed650c3d110084e53cbf0a3a23c

e4f91fb0b91c71e73904c162db26e73d1877941cb22513af62fa6db7c06f40c4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sentinelone-sdk (2 malicious versions).
If you installed it — respond
Remove sentinelone-sdk 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-sdk 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-sdk on PyPI has been identified as a malicious package (versions 6.2.1, 6.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04789RLUA-2024-09252

References

Credits

ReversingLabs · finder

Detect & block this

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