Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in internallib_v811 (npm)

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 internallib_v811

    Affected
    >= 1.0.1, <= 1.0.1
    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 (cee312ec1c8c2f9177c54179b22a3f493ba30ee35b5f3c41952b5bdbbfd4eed0) package.json declares the dependency `internallib-helper` with a source of `http://10.0.77.5:8000/internallib-helper-1.0.1.tgz` — a plain-HTTP tarball URL on a private IP, not a registry version range. On `npm install`, npm fetches whatever bytes that host serves and installs them, executing any lifecycle scripts inside the fetched tarball, with no version pin and no integrity check. The transport is cleartext HTTP, so any party able to intercept traffic to 10.0.77.5:8000 can substitute the delivered archive. The shipped `index.js` is a trivial stub, so the manifest line itself is the install-time code-delivery mechanism. The dependency name `internallib-helper` closely mirrors the package's own name `internallib_v811`, matching an internal-package / dependency-confusion lure shape.

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

Agent brief

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

# Patch Next advisory brief: mal-2026-19230

Advisory: Malicious code in internallib_v811 (npm)
IDs: mal-2026-19230
Record: https://patchnext.com/advisories/mal-2026-19230 (revision 1, source checked 13 Nov 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 internallib_v811: affected >= 1.0.1, <= 1.0.1

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

Commands are suggestions: review each one before running it.

Loading voting…