Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍 PyPI
Not in CISA KEV

GHSA-g86j-hwg9-77q5 sentinelone

GHSA-g86j-hwg9-77q5 is a security vulnerability in sentinelone. No vendor fix is recorded yet; mitigation options are listed below.

SentinelOne impersonated via PyPI packages

Published
Dec 27, 2022
Updated
Dec 27, 2022
Affected
5 pkgs
Patched
None yet
Exploits
None indexed
Exploitation data as of Dec 27, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

5 pkgs affected
🐍sentinelone🐍sentinelone-sdk🐍sentinelonesdk🐍sentinelone🐍sentinelonesdk

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

In December 2022, threat actors impersonated SentinelOne by uploading fake software development kits (SDKs) onto PyPI. The SDKs contain fully functional SentinelOne clients, but the packages also contained malicious backdoors that are only executed when called on programmatically, as opposed to during installation. The packages have since been taken down from PyPI.

Affected Packages

5 total
EcosystemPackageVulnerable rangeFix
🐍PyPIsentinelone1.0.0No fix
🐍PyPIsentinelone-sdk6.2.1No fix
🐍PyPIsentinelonesdkall versionsNo fix
🐍PyPIsentineloneall versionsNo fix
🐍PyPIsentinelonesdkall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sentinelone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of sentinelone has shipped for GHSA-g86j-hwg9-77q5 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g86j-hwg9-77q5 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-g86j-hwg9-77q5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In December 2022, threat actors impersonated SentinelOne by uploading fake software development kits (SDKs) onto PyPI. The SDKs contain fully functional SentinelOne clients, but the packages also contained malicious backdoors that are only executed when called on programmatically, as opposed to during installation. The packages have since been taken down from PyPI.
O3 Security · Impact-Aware SCA

Is GHSA-g86j-hwg9-77q5 in your dependencies?

O3 Security finds GHSA-g86j-hwg9-77q5 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-g86j-hwg9-77q5: sentinelone | O3 Security