# MAL-2026-10138: Malicious code in uac-package (npm)


- **Type:** Malicious package
- **Package:** `uac-package` (npm)
- **Published:** 10 Jul 2026
- **Also known as:** GHSA-7cmm-649r-p3q2

## What is MAL-2026-10138?

MAL-2026-10138 is a malicious package in uac-package, published on 10 Jul 2026. 

### Official description

uac-package@1.4.4 is an analytics package that, on install, silently mutates the installer's project files: postinstall.js invokes integrate() which rewrites package.json scripts (dev/preview/start), edits vite.config.*/nuxt.config.*, and prepends `import 'uac-package/track'` to the first matching src/main.{js,ts,tsx,jsx} or src/index.{js,ts}. All mutations reference only the package's own modules; no remote code is fetched at install time. The injected runtime module (autoIdentity.mjs) runs later in the deployed app's browser and performs broad end-user identity extraction: it scans localStorage/sessionStorage against a large auth-key list (access_token, id_token, refresh_token, jwt, persist:auth, okta-token-storage, firebase:authUser, @auth0spajs, msal.account.keys, CognitoIdentityServiceProvider, supabase.auth.token, Clerk/Amplify/Keycloak keys), decodes JWTs, reads auth cookies, and monkey-patches window.fetch and XMLHttpRequest to intercept auth-related responses; extracted name/email/custom fields are POSTed to https://uac-backend.clay.in. The install-time mutation targets the installer's project only and references first-party modules (no exfil, RCE, credential theft, or destruction on the installer's machine). The auth-token collection executes in the installer's end-users' browsers after deployment — the developer opts into this by installing an analytics package that advertises identity tracking, and the destination is the vendor's documented backend — so it is not a supply-chain attack on the installer, but the identity-extraction scope (broad auth-key list, fetch/XHR interception, JWT decoding) is materially broader than typical product analytics and may create downstream privacy/compliance exposure for the installer's end-users.

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-10138?

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-10138 is a malicious package: uac-package (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-10138/ (Markdown: https://insights.sbomify.com/MAL-2026-10138/index.md)
```

## Sources

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

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