Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in claims-acct-unlock (npm)

GHSA-7338-2qv3-86fw

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.

Add to your agent

Affected packages

  • npm claims-acct-unlock

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

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.

--- _-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (fe5161ec5e3bb6bc18d6975809d09281190c49b41a4f926dfa6a28cabf061e04) claims-acct-unlock@25.2.1 ships no source code; package.json declares a single dependency 'node-acct-utilssss21' resolved from a bare HTTPS tarball URL on an unrelated GitHub user's repository (github.com/GamerD11/ping_test) at the mutable branch ref refs/heads/main, with no commit pin and no integrity hash. On npm install, npm fetches whatever bytes are currently served at that URL and installs them as a dependency, running any lifecycle scripts bundled inside. The repository owner can replace the tarball contents at any time without any change to this package. The dependency name does not correspond to a known library and resembles a typo of an internal/utility package, consistent with a dependency-confusion / lure shape where the manifest itself is the entire attack surface.

Source: ghsa-malware…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record MAL-2026-18404

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-7338-2qv3-86fw

Advisory: Malicious code in claims-acct-unlock (npm)
IDs: GHSA-7338-2qv3-86fw
Record: https://patchnext.com/advisories/mal-2026-18404 (revision 1, source checked 31 Oct 2026, 06:00 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 claims-acct-unlock: affected every version

## Suggested inspection (read-only)
- `npm ls claims-acct-unlock --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 claims-acct-unlock.
- 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-18404 (OSV record MAL-2026-18404 lists affected ranges: npm claims-acct-unlock >=0)

Commands are suggestions: review each one before running it.

Loading voting…