Skip to content

← Actionable
Unratedamended

Malicious code in @iobandamwer/native-helper (npm)

GHSA-g457-v22r-g8j3

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 @iobandamwer/native-helper

    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 (cce0282c2e8975376db9fdb7a69afc7ed77c0e7649178967496467e09d7ba328) The package self-labels as a 'temporary placeholder stub' in package.json and README but ships active install-time dropper artifacts: a 93-byte index.js that loads a native addon (addon.node ELF for Linux, addon_win.node PE for Windows), an 8 MB opaque.napi_cache blob, and a postinstall script that calls addon.init() during npm install. The native addon decodes the shipped.napi_cache blob, writes it to a hidden temp path (/tmp/. on Linux,.nc .js on Windows), chmods it executable, and detaches it via fork + setsid + execlp so it continues to run after npm install completes. Before executing the dropped payload, the addon checks for CI environment variables (GITHUB_ACTIONS, GITLAB_CI, CIRCLECI, JENKINS_URL, BUILDKITE, CODEBUILD_BUILD_ID, APPVEYOR, SEMAPHORE, TEAMCITY_VERSION, BITBUCKET_BUILD_NUMBER, NOW_GITHUB_DEPLOYMENT,…

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

  2. Revision 1 · created ·

    Published from osv record MAL-2026-18330

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-g457-v22r-g8j3

Advisory: Malicious code in @iobandamwer/native-helper (npm)
IDs: GHSA-g457-v22r-g8j3
Record: https://patchnext.com/advisories/mal-2026-18330 (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 @iobandamwer/native-helper: affected every version

## Suggested inspection (read-only)
- `npm ls @iobandamwer/native-helper --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 @iobandamwer/native-helper.
- 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-18330 (OSV record MAL-2026-18330 lists affected ranges: npm @iobandamwer/native-helper >=0)

Commands are suggestions: review each one before running it.

Loading voting…