Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Malicious code in tostpro (npm)

GHSA-x5qq-j2hm-34m3

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 tostpro

    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 (7785c0ac37ad4bb74abc644be2a5fc48bdb0d1248027e607fdf13ddaaa59d546) Package tostpro@99.101.0 declares scripts.preinstall='sh./rce_poc.sh'. On install, the shipped shell script runs id/hostname/pwd and appends a timestamped line to./RCE_POC_MARKER.txt in the installer's working directory. The script performs no network I/O, reads no credentials or environment, writes nothing outside the install tree, and installs no persistence. The declared main entry dist/index.js is not shipped in the tarball, so the package has no library/import-time behavior; the preinstall marker write is its only effect. The README identifies the package as a security-research canary demonstrating dependency-confusion exposure for an internal name, consistent with the implausibly high version (99.101.0) used to win resolution against an internal package. The preinstall execution path is a real supply-chain concern in…

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-17564

  2. Revision 1 · created ·

    Published from osv record MAL-2026-17564

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-x5qq-j2hm-34m3

Advisory: Malicious code in tostpro (npm)
IDs: GHSA-x5qq-j2hm-34m3
Record: https://patchnext.com/advisories/mal-2026-17564 (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 tostpro: affected every version

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

Commands are suggestions: review each one before running it.

Loading voting…