{"items":[{"id":"NVI-00009637","kind":"supply_chain_event","title":"Malicious code in some-very-long-package-name (npm)","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-rf49-p2c5-fh8p"],"plain_summary":"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.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-18b4dee4bbb6612f62e37238835b13b3"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-18b4dee4bbb6612f62e37238835b13b3","url":"https://github.com/advisories/GHSA-rf49-p2c5-fh8p","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-rf49-p2c5-fh8p","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:53.250Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-18b4dee4bbb6612f62e37238835b13b3"],"technology":"some-very-long-package-name","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (1ce120698c1be7e98866ccdff0987f7b77f53377e525284f311363b79f5ea397)\nPackage 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.\n\n---\n\nCredit: OpenSSF (source)","public_affected_ranges":["= 2.0.0"]},{"certainty":"source_listed","source_ids":["sr-18b4dee4bbb6612f62e37238835b13b3"],"technology":"some-very-long-package-name","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (1ce120698c1be7e98866ccdff0987f7b77f53377e525284f311363b79f5ea397)\nPackage 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.\n\n---\n\nCredit: OpenSSF (source)","public_affected_ranges":["= 1.0.0"]},{"certainty":"source_listed","source_ids":["sr-18b4dee4bbb6612f62e37238835b13b3"],"technology":"some-very-long-package-name","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (1ce120698c1be7e98866ccdff0987f7b77f53377e525284f311363b79f5ea397)\nPackage 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.\n\n---\n\nCredit: OpenSSF (source)","public_affected_ranges":["= 3.0.0"]},{"certainty":"source_listed","source_ids":["sr-18b4dee4bbb6612f62e37238835b13b3"],"technology":"some-very-long-package-name","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (1ce120698c1be7e98866ccdff0987f7b77f53377e525284f311363b79f5ea397)\nPackage 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.\n\n---\n\nCredit: OpenSSF (source)","public_affected_ranges":["= 2.0.1"]},{"certainty":"source_listed","source_ids":["sr-18b4dee4bbb6612f62e37238835b13b3"],"technology":"some-very-long-package-name","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (1ce120698c1be7e98866ccdff0987f7b77f53377e525284f311363b79f5ea397)\nPackage 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.\n\n---\n\nCredit: OpenSSF (source)","public_affected_ranges":["= 99.0.1"]}],"null_published_at":"2026-10-31T22:13:39.926Z","source_updated_at":"2026-10-11T18:31:29.000Z","source_disclosed_at":"2026-10-11T15:31:12.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T22:06:53.250Z"}],"next_cursor":null,"snapshot_revision":"42594"}