# MAL-2026-10422: Malicious code in sso-users-detection (npm)


- **Type:** Malicious package
- **Package:** `sso-users-detection` (npm)
- **Published:** 13 Jul 2026
- **Also known as:** GHSA-x9p4-637q-6wjw

## What is MAL-2026-10422?

MAL-2026-10422 is a malicious package in sso-users-detection, published on 13 Jul 2026. 

### Official description

sso-users-detection@99.9.1 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.

## What should I do about MAL-2026-10422?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-10422 is a malicious package: sso-users-detection (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-10422/ (Markdown: https://insights.sbomify.com/MAL-2026-10422/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-10422

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-10422/
Summaries are generated and may contain mistakes; the official description above is the record.