GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

MAL-2026-18333unknown

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

No CVE assignedReported malicious packageCheck your stack

The advisory, in context


-= 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 indicators (GITHUB_ACTIONS, GITLAB_CI, TRAVIS, CIRCLECI, SANDBOX, JENKINS_URL, BUILDKITE, CODEBUILD_BUILD_ID, APPVEYOR, SEMAPHORE, TEAMCITY_VERSION, BITBUCKET_BUILD_NUMBER, NETLIFY, VERCEL, CF_BUILD_ID, SCREWDRIVER), reads /proc/1/cgroup and /proc/1/cmdline for container markers (docker, containerd, kubepod, sandbox, podman), and inspects /proc/self/status for TracerPid, gating execution to non-analysis hosts. The payload bytes themselves are packed/encrypted and not inspectable from the tarball. A placeholder stub has no legitimate reason to ship a native dropper, detach a hidden /tmp child, and evade sandboxes.

Source: ghsa-malware (910dd2c3846dd989ee98147187c379760a3d055ffe413f85d36def235d6a7cf7)

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.

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

Versions

All releases from the beginning; no upper bound recorded

No fix recorded for this interval.

4 explicitly affected versions

0.0.3, 0.0.2, 0.0.1, 0.0.4

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        }
      ],
      "type": "SEMVER"
    }
  ],
  "versions": [
    "0.0.3",
    "0.0.2",
    "0.0.1",
    "0.0.4"
  ]
}

References