uac-package
Affected
- Versions:
1.1.0,1.1.1,1.1.2,1.1.3,1.2.1,1.3.0,1.4.0,1.4.1,1.4.3,1.4.4,1.4.5,1.4.6,1.4.7,1.4.8
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-7cmm-649r-p3q2
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in uac-package (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (cb2f1cf2dbbdb87f2b0c37826d8326ff0ca7ecfdbc3af1dd4fdd31a0c299c78b)
[email protected] 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.
Source: ghsa-malware (ecd1d3f24d31780d5f1db222bced091f2c311926df12057168bfff46c1bc2a6d)
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.
Not rated by the source.
1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.2.1, 1.3.0, 1.4.0, 1.4.1, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.8None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0