Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Malicious code in @webapp-shared/login-vmok (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 @webapp-shared/login-vmok

    Affected
    >= 1.0.0, <= 1.0.0>= 1.0.1, <= 1.0.1>= 1.1.0, <= 1.1.0>= 2.0.1, <= 2.0.1>= 3.0.0, <= 3.0.0>= 99.0.1, <= 99.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.

@webapp-shared/login-vmok is a dependency-confusion package: it uses the `@webapp-shared` scope, which matches a private internal package scope, and was published on 2026-10-27 in versions 1.0.0, 1.0.1, 1.1.0, 2.0.1, 3.0.0 and 99.0.1 so that builds resolving the internal name from the public registry install it instead. Its `postinstall` script runs `node beacon.cjs`, which sends an HTTP POST over cleartext HTTP to the hardcoded IP endpoint `http://13.140.137.222:8787/_ah/dc` with the package name, the machine's hostname, the install directory, the current working directory and the Node.js version; the entry point `index.js` sends the same request again whenever the package is loaded and otherwise has no functionality. The beacon code is the same as in other dependency-confusion packages sending to `http://185.158.107.175:8787/_ah/dc` (e.g. MAL-2026-18276), with only the endpoint and package name changed. The inert `0.0.0-stage` and `0.1.0` placeholder versions carry no install…

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

  2. Revision 1 · created ·

    Published from osv record MAL-2026-18356

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

Advisory: Malicious code in @webapp-shared/login-vmok (npm)
IDs: mal-2026-18356
Record: https://patchnext.com/advisories/mal-2026-18356 (revision 2, source checked 30 Oct 2026, 06:15 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 @webapp-shared/login-vmok: affected >= 1.0.0, <= 1.0.0; >= 1.0.1, <= 1.0.1; >= 1.1.0, <= 1.1.0; >= 2.0.1, <= 2.0.1; >= 3.0.0, <= 3.0.0; >= 99.0.1, <= 99.0.1

## Suggested inspection (read-only)
- `npm ls @webapp-shared/login-vmok --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 @webapp-shared/login-vmok.
- 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-18356 (OSV record MAL-2026-18356 lists affected ranges: npm @webapp-shared/login-vmok >=1.0.0 =1.0.1 =1.1.0 =2.0.1 =3.0.0 =99.0.1 <=99.0.1)

Commands are suggestions: review each one before running it.

Loading voting…