Malicious code in @drone-js-ext/vip-badge (npm)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

@drone-js-ext/vip-badge is a dependency-confusion package: it squats the `@drone-js-ext` scope, which matches a private internal package scope, and was published on 2026-10-25 in versions 0.0.1, 1.0.1, 2.0.0, 99.0.1 (up to 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://185.158.107.175:8787/_ah/dc` with the package name, the machine's hostname, the install directory, the current working directory and the Node.js version, tagged with an `x-beacon-package` header. The entry point `index.js` sends the same request again whenever the package is loaded and otherwise exports a Proxy whose every property is a no-op function, so it has no legitimate functionality and hides the missing API from bundlers. The README calls it an "authorized dependency-confusion test"; that does not change what it does to an installer.…

Published by the source

25 Oct 2026, 04:50 UTC

Last modified by the source

29 Oct 2026, 14:45 UTC

Source last checked

30 Oct 2026, 06:00 UTC

1. Revision 4 · amended · 30 Oct 2026

   Amended from osv record MAL-2026-18277

2. Revision 3 · amended · 29 Oct 2026

   Amended from osv record MAL-2026-18277

3. Revision 2 · amended · 27 Oct 2026

   Amended from osv record MAL-2026-18277

4. Revision 1 · created · 26 Oct 2026

   Published from osv record MAL-2026-18277

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

# Patch Next advisory brief: GHSA-h7v8-65vw-r7wh

Advisory: Malicious code in @drone-js-ext/vip-badge (npm)
IDs: GHSA-h7v8-65vw-r7wh
Record: https://patchnext.com/advisories/mal-2026-18277 (revision 4, source checked 30 Oct 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 @drone-js-ext/vip-badge: affected every version

## Suggested inspection (read-only)
- `npm ls @drone-js-ext/vip-badge --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 @drone-js-ext/vip-badge.
- 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-18277 (OSV record MAL-2026-18277 lists affected ranges: npm @drone-js-ext/vip-badge >=99.0.1 =0.0.1 =2.0.0 =1.0.1 <=1.0.1)
- Verified: https://osv.dev/vulnerability/MAL-2026-18277 (OSV record MAL-2026-18277 lists affected ranges: npm @drone-js-ext/vip-badge >=0)

Commands are suggestions: review each one before running it.