Which versions of sso-users-detection are malicious?

The following npm versions of sso-users-detection are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate sso-users-detection if I installed it?

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

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

Yes — sso-users-detection is associated with the IN-MAL-2026-009852 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 sso-users-detection 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 sso-users-detection (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sso-users-detection across your stack and pipelines.

Malicious package

sso-users-detectionnpm

Malicious code in sso-users-detection (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10422

Immediate action

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

npm uninstall sso-users-detection

What this malware does

[email protected] is a hollow package (main exports {}, empty author/description, inflated 99.9.1 version) whose sole effect on install is to pull a runtime dependency named ltidisafe from a raw tarball URL on a third-party Google Cloud Storage bucket (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.3.1.tgz) instead of the npm registry. On npm install, npm fetches and installs that tarball, whose contents and lifecycle scripts (preinstall/install/postinstall) are entirely controlled by whoever owns the bucket and bypass npm registry scanning. The depenconf path segment, the inflated version number, and the empty index are consistent with a dependency-confusion lure whose only purpose is to smuggle attacker-controlled code into installer dependency trees.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

dc80441472ec24451f83aebdc186d5bc532ddadaac8888d3d30b72c17c94f993

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

Campaign

IN-MAL-2026-009852

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks sso-users-detection-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