Malicious code in @azure-growth/signup-ux-components (npm)
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm @azure-growth/signup-ux-components
- Affected
- >= 1.2.2, <= 1.2.2>= 1.2.3, <= 1.2.3>= 2.9.9, <= 2.9.9
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-18338 lists affected ranges: npm @azure-growth/signup-ux-components >=1.2.2 =1.2.3 <=1.2.3
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-18338 lists affected ranges: npm @azure-growth/signup-ux-components >=1.2.2 =1.2.3 =2.9.9 <=2.9.9
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
@azure-growth/signup-ux-components 1.2.2, 1.2.3 and 2.9.9 are dependency-confusion packages that take the name of a package used internally by Microsoft's Azure signup site and not published on the npm registry; 2.9.9 carries a version number above the internal release, so resolvers that also check the public registry prefer it. Their `preinstall` script runs `node index.js`, which reads the OS username and hostname and sends them in a DNS lookup of `msrc-poc. . .dbg6vplohjpkmtolbi6g18ekofkxjzm4s.oast.fun`, an out-of-band interaction collector; `index.js` is also the package entry point, so the lookup repeats whenever the package is required. Any machine that installed one of these versions has disclosed its username and hostname to a third party. The earlier `0.0.0-stage` version is an inert placeholder and is not affected. --- _-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (e6d15071d1e0d5aba0263de2826a4fde28064184bd5b38b1294a0ad1493069ef) The…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from osv record MAL-2026-18338
- Revision 2 · amended ·
Amended from osv record MAL-2026-18338
- Revision 1 · created ·
Published from osv record MAL-2026-18338
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: mal-2026-18338 Advisory: Malicious code in @azure-growth/signup-ux-components (npm) IDs: mal-2026-18338 Record: https://patchnext.com/advisories/mal-2026-18338 (revision 3, source checked 30 Oct 2026, 06:15 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @azure-growth/signup-ux-components: affected >= 1.2.2, <= 1.2.2; >= 1.2.3, <= 1.2.3; >= 2.9.9, <= 2.9.9 ## Suggested inspection (read-only) - `npm ls @azure-growth/signup-ux-components --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @azure-growth/signup-ux-components. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/MAL-2026-18338 (OSV record MAL-2026-18338 lists affected ranges: npm @azure-growth/signup-ux-components >=1.2.2 =1.2.3 <=1.2.3) - Verified: https://osv.dev/vulnerability/MAL-2026-18338 (OSV record MAL-2026-18338 lists affected ranges: npm @azure-growth/signup-ux-components >=1.2.2 =1.2.3 =2.9.9 <=2.9.9) Commands are suggestions: review each one before running it.
Loading voting…