supply chain event / NVI-00009637 / Revision 1
Malicious code in some-very-long-package-name (npm)
GitHub lists this malware advisory for some-very-long-package-name, some-very-long-package-name, some-very-long-package-name, some-very-long-package-name, some-very-long-package-name. 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.
some-very-long-package-name
source listed= 2.0.0
## Source: amazon-inspector (1ce120698c1be7e98866ccdff0987f7b77f53377e525284f311363b79f5ea397) Package ships a `postinstall` lifecycle hook (`node beacon.cjs`) and a top-level `require('./beacon.cjs').fire()` call in index.js, so both `npm install` and any `require()` of the package trigger an outbound HTTP POST to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The POST body is a JSON payload containing the installer's hostname (`os.hostname()`), the install path (`__dirname`), the current working directory (`process.cwd()`), and the Node.js version. The package exports no real functionality: index.js returns a Proxy whose property accesses all resolve to a no-op function, so the module's only effect is the beacon. The self-description as a 'Compatibility shim' combined with the generic package name and the no-op surface is consistent with a dependency-confusion / name-squat callback package targeting an internal package name. --- Credit: OpenSSF (source)
some-very-long-package-name
source listed= 1.0.0
## Source: amazon-inspector (1ce120698c1be7e98866ccdff0987f7b77f53377e525284f311363b79f5ea397) Package ships a `postinstall` lifecycle hook (`node beacon.cjs`) and a top-level `require('./beacon.cjs').fire()` call in index.js, so both `npm install` and any `require()` of the package trigger an outbound HTTP POST to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The POST body is a JSON payload containing the installer's hostname (`os.hostname()`), the install path (`__dirname`), the current working directory (`process.cwd()`), and the Node.js version. The package exports no real functionality: index.js returns a Proxy whose property accesses all resolve to a no-op function, so the module's only effect is the beacon. The self-description as a 'Compatibility shim' combined with the generic package name and the no-op surface is consistent with a dependency-confusion / name-squat callback package targeting an internal package name. --- Credit: OpenSSF (source)
some-very-long-package-name
source listed= 3.0.0
## Source: amazon-inspector (1ce120698c1be7e98866ccdff0987f7b77f53377e525284f311363b79f5ea397) Package ships a `postinstall` lifecycle hook (`node beacon.cjs`) and a top-level `require('./beacon.cjs').fire()` call in index.js, so both `npm install` and any `require()` of the package trigger an outbound HTTP POST to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The POST body is a JSON payload containing the installer's hostname (`os.hostname()`), the install path (`__dirname`), the current working directory (`process.cwd()`), and the Node.js version. The package exports no real functionality: index.js returns a Proxy whose property accesses all resolve to a no-op function, so the module's only effect is the beacon. The self-description as a 'Compatibility shim' combined with the generic package name and the no-op surface is consistent with a dependency-confusion / name-squat callback package targeting an internal package name. --- Credit: OpenSSF (source)
some-very-long-package-name
source listed= 2.0.1
## Source: amazon-inspector (1ce120698c1be7e98866ccdff0987f7b77f53377e525284f311363b79f5ea397) Package ships a `postinstall` lifecycle hook (`node beacon.cjs`) and a top-level `require('./beacon.cjs').fire()` call in index.js, so both `npm install` and any `require()` of the package trigger an outbound HTTP POST to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The POST body is a JSON payload containing the installer's hostname (`os.hostname()`), the install path (`__dirname`), the current working directory (`process.cwd()`), and the Node.js version. The package exports no real functionality: index.js returns a Proxy whose property accesses all resolve to a no-op function, so the module's only effect is the beacon. The self-description as a 'Compatibility shim' combined with the generic package name and the no-op surface is consistent with a dependency-confusion / name-squat callback package targeting an internal package name. --- Credit: OpenSSF (source)
some-very-long-package-name
source listed= 99.0.1
## Source: amazon-inspector (1ce120698c1be7e98866ccdff0987f7b77f53377e525284f311363b79f5ea397) Package ships a `postinstall` lifecycle hook (`node beacon.cjs`) and a top-level `require('./beacon.cjs').fire()` call in index.js, so both `npm install` and any `require()` of the package trigger an outbound HTTP POST to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The POST body is a JSON payload containing the installer's hostname (`os.hostname()`), the install path (`__dirname`), the current working directory (`process.cwd()`), and the Node.js version. The package exports no real functionality: index.js returns a Proxy whose property accesses all resolve to a no-op function, so the module's only effect is the beacon. The self-description as a 'Compatibility shim' combined with the generic package name and the no-op surface is consistent with a dependency-confusion / name-squat callback package targeting an internal package name. --- 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-rf49-p2c5-fh8p ↗
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.