supply chain event / NVI-00009636 / Revision 1
Malicious code in cloudflare_module (npm)
GitHub lists this malware advisory for cloudflare_module, cloudflare_module, cloudflare_module, cloudflare_module. 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.
cloudflare_module
source listed= 3.0.0
## Source: amazon-inspector (14316e66f8d8eeb53b5fd4850537ac5398947feaf88f3837e39bfa587f60a0fb) cloudflare_module@1.0.1 is a typosquat of Cloudflare branding whose only functional code is an install- and import-time beacon. beacon.cjs defines BEACON = "http://185.158.107.175:8787/_ah/dc" and a fire() function that POSTs a JSON payload containing os.hostname(), __dirname (installPath), process.cwd(), process.version and the package name to that hardcoded bare-IP HTTP endpoint. fire() is invoked from the package's postinstall script, so it runs automatically on `npm install`, and from the main module, so it also runs on `require('cloudflare_module')`. The package's main entry exports a Proxy of no-op functions (`module.exports = new Proxy({}, { get:... return _noop; })`) with a generic "Compatibility shim" description, so the package provides no legitimate functionality — the exfil beacon is its sole behavior. The destination is a bare IPv4 address on a non-standard port over cleartext HTTP, with no relationship to Cloudflare or any documented publisher. Host identity, install path and working directory shipped to an attacker-controlled collector constitute reconnaissance of installer
cloudflare_module
source listed= 1.0.1
## Source: amazon-inspector (14316e66f8d8eeb53b5fd4850537ac5398947feaf88f3837e39bfa587f60a0fb) cloudflare_module@1.0.1 is a typosquat of Cloudflare branding whose only functional code is an install- and import-time beacon. beacon.cjs defines BEACON = "http://185.158.107.175:8787/_ah/dc" and a fire() function that POSTs a JSON payload containing os.hostname(), __dirname (installPath), process.cwd(), process.version and the package name to that hardcoded bare-IP HTTP endpoint. fire() is invoked from the package's postinstall script, so it runs automatically on `npm install`, and from the main module, so it also runs on `require('cloudflare_module')`. The package's main entry exports a Proxy of no-op functions (`module.exports = new Proxy({}, { get:... return _noop; })`) with a generic "Compatibility shim" description, so the package provides no legitimate functionality — the exfil beacon is its sole behavior. The destination is a bare IPv4 address on a non-standard port over cleartext HTTP, with no relationship to Cloudflare or any documented publisher. Host identity, install path and working directory shipped to an attacker-controlled collector constitute reconnaissance of installer
cloudflare_module
source listed= 1.0.0
## Source: amazon-inspector (14316e66f8d8eeb53b5fd4850537ac5398947feaf88f3837e39bfa587f60a0fb) cloudflare_module@1.0.1 is a typosquat of Cloudflare branding whose only functional code is an install- and import-time beacon. beacon.cjs defines BEACON = "http://185.158.107.175:8787/_ah/dc" and a fire() function that POSTs a JSON payload containing os.hostname(), __dirname (installPath), process.cwd(), process.version and the package name to that hardcoded bare-IP HTTP endpoint. fire() is invoked from the package's postinstall script, so it runs automatically on `npm install`, and from the main module, so it also runs on `require('cloudflare_module')`. The package's main entry exports a Proxy of no-op functions (`module.exports = new Proxy({}, { get:... return _noop; })`) with a generic "Compatibility shim" description, so the package provides no legitimate functionality — the exfil beacon is its sole behavior. The destination is a bare IPv4 address on a non-standard port over cleartext HTTP, with no relationship to Cloudflare or any documented publisher. Host identity, install path and working directory shipped to an attacker-controlled collector constitute reconnaissance of installer
cloudflare_module
source listed= 99.0.1
## Source: amazon-inspector (14316e66f8d8eeb53b5fd4850537ac5398947feaf88f3837e39bfa587f60a0fb) cloudflare_module@1.0.1 is a typosquat of Cloudflare branding whose only functional code is an install- and import-time beacon. beacon.cjs defines BEACON = "http://185.158.107.175:8787/_ah/dc" and a fire() function that POSTs a JSON payload containing os.hostname(), __dirname (installPath), process.cwd(), process.version and the package name to that hardcoded bare-IP HTTP endpoint. fire() is invoked from the package's postinstall script, so it runs automatically on `npm install`, and from the main module, so it also runs on `require('cloudflare_module')`. The package's main entry exports a Proxy of no-op functions (`module.exports = new Proxy({}, { get:... return _noop; })`) with a generic "Compatibility shim" description, so the package provides no legitimate functionality — the exfil beacon is its sole behavior. The destination is a bare IPv4 address on a non-standard port over cleartext HTTP, with no relationship to Cloudflare or any documented publisher. Host identity, install path and working directory shipped to an attacker-controlled collector constitute reconnaissance of installer
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-9p5g-9jf3-6739 ↗
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.