supply chain event / NVI-00008410 / Revision 1
Malicious code in @drone-js-ext/vip-badge (npm)
GitHub lists this malware advisory for @drone-js-ext/vip-badge, @drone-js-ext/vip-badge, @drone-js-ext/vip-badge, @drone-js-ext/vip-badge. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
@drone-js-ext/vip-badge
source listed= 99.0.1
## Source: amazon-inspector (2f7afa65da63d3360d15659ebdcce5f5078fa7bd210e04c069f88834f0c1f75c) The package is a zero-functionality stub whose main module (index.js) exports a Proxy returning no-op functions for any property access. Its only real behavior is a beacon implemented in beacon.cjs that collects installer host identifiers (os.hostname(), __dirname, process.cwd(), process.version, and related os/process fields) and POSTs them over plain HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The beacon fires both from the postinstall lifecycle script (triggered automatically by npm install) and at require() time of the main entry. The destination is not a publisher-owned domain, is not configurable, and is not disclosed. The scoped name, implausibly high version (99.0.1), stub implementation, and install-time recon beacon are consistent with a dependency-confusion or typosquat probe harvesting internal installs. --- Credit: OpenSSF (source)
@drone-js-ext/vip-badge
source listed= 0.0.1
## Source: amazon-inspector (2f7afa65da63d3360d15659ebdcce5f5078fa7bd210e04c069f88834f0c1f75c) The package is a zero-functionality stub whose main module (index.js) exports a Proxy returning no-op functions for any property access. Its only real behavior is a beacon implemented in beacon.cjs that collects installer host identifiers (os.hostname(), __dirname, process.cwd(), process.version, and related os/process fields) and POSTs them over plain HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The beacon fires both from the postinstall lifecycle script (triggered automatically by npm install) and at require() time of the main entry. The destination is not a publisher-owned domain, is not configurable, and is not disclosed. The scoped name, implausibly high version (99.0.1), stub implementation, and install-time recon beacon are consistent with a dependency-confusion or typosquat probe harvesting internal installs. --- Credit: OpenSSF (source)
@drone-js-ext/vip-badge
source listed= 2.0.0
## Source: amazon-inspector (2f7afa65da63d3360d15659ebdcce5f5078fa7bd210e04c069f88834f0c1f75c) The package is a zero-functionality stub whose main module (index.js) exports a Proxy returning no-op functions for any property access. Its only real behavior is a beacon implemented in beacon.cjs that collects installer host identifiers (os.hostname(), __dirname, process.cwd(), process.version, and related os/process fields) and POSTs them over plain HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The beacon fires both from the postinstall lifecycle script (triggered automatically by npm install) and at require() time of the main entry. The destination is not a publisher-owned domain, is not configurable, and is not disclosed. The scoped name, implausibly high version (99.0.1), stub implementation, and install-time recon beacon are consistent with a dependency-confusion or typosquat probe harvesting internal installs. --- Credit: OpenSSF (source)
@drone-js-ext/vip-badge
source listed= 1.0.1
## Source: amazon-inspector (2f7afa65da63d3360d15659ebdcce5f5078fa7bd210e04c069f88834f0c1f75c) The package is a zero-functionality stub whose main module (index.js) exports a Proxy returning no-op functions for any property access. Its only real behavior is a beacon implemented in beacon.cjs that collects installer host identifiers (os.hostname(), __dirname, process.cwd(), process.version, and related os/process fields) and POSTs them over plain HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The beacon fires both from the postinstall lifecycle script (triggered automatically by npm install) and at require() time of the main entry. The destination is not a publisher-owned domain, is not configurable, and is not disclosed. The scoped name, implausibly high version (99.0.1), stub implementation, and install-time recon beacon are consistent with a dependency-confusion or typosquat probe harvesting internal installs. --- Credit: OpenSSF (source)
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-g6h7-w896-4p29 ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.