Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Malicious code in path-stream-utils-testmetest (npm)

GHSA-7pvr-f92m-6fwg

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 path-stream-utils-testmetest

    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 (64a028e4ea3039755f4b18b003e2d9722722ca96c51652674dd1bb27f375e4d0) The package self-describes as a 'Temporary package placeholder for staged publishing' (package.json stub:true, README 'Temporary Holding Version') but ships a Linux addon.node, a Windows.node, and a 6,052,359-byte opaque.napi_cache blob containing no printable strings. package.json defines a postinstall that executes `node -e "require('./addon.node').init()"`, and index.js requires and invokes the same init(). On invocation the native addon reads the sibling.napi_cache file (format string '%s/.napi_cache'), writes the bytes to a PID-named hidden file under /tmp (format '/tmp/.%u'), chmods it executable, and detaches a child via fork+setsid+execlp, so the opaque payload runs under the installer's user on npm install and on every require() of the package. Before executing the dropped file the addon enumerates CI and sandbox…

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

    Amended from osv record MAL-2026-18333

  2. Revision 1 · created ·

    Published from osv record MAL-2026-18333

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-7pvr-f92m-6fwg

Advisory: Malicious code in path-stream-utils-testmetest (npm)
IDs: GHSA-7pvr-f92m-6fwg
Record: https://patchnext.com/advisories/mal-2026-18333 (revision 2, source checked 30 Oct 2026, 06:05 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 path-stream-utils-testmetest: affected every version

## Suggested inspection (read-only)
- `npm ls path-stream-utils-testmetest --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 path-stream-utils-testmetest.
- 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-18333 (OSV record MAL-2026-18333 lists affected ranges: npm path-stream-utils-testmetest >=0)

Commands are suggestions: review each one before running it.

Loading voting…