NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

sso-users-detectionnpm

Advisory published Updated

sso-users-detection is a confirmed malicious npm package (MAL-2026-10422) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sso-users-detection (npm)

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.

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

1 flagged
99.9.1

Indicators of compromise (SHA-256)

dc80441472ec24451f83aebdc186d5bc532ddadaac8888d3d30b72c17c94f993
7838ee283b14ef927649c5f9561d72fdf44314123606f78f4201a15d589696c6

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for sso-users-detection (version 99.9.1).

  2. 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.

  3. Did it already run?

    If sso-users-detection 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. 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-009852GHSA-x9p4-637q-6wjw

References

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.

Explore

sso-users-detection (npm) malicious package — MAL-2026-10422 | O3 Security