{"items":[{"id":"NVI-00008553","kind":"supply_chain_event","title":"Malicious code in @ppa-web-components/ppa-banner (npm)","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-2g28-gqgq-ghvf"],"plain_summary":"GitHub lists this malware advisory for @ppa-web-components/ppa-banner, @ppa-web-components/ppa-banner, @ppa-web-components/ppa-banner, @ppa-web-components/ppa-banner, @ppa-web-components/ppa-banner. 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-6c882745c639e2b474fac90ea739d336"],"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-6c882745c639e2b474fac90ea739d336","url":"https://github.com/advisories/GHSA-2g28-gqgq-ghvf","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-2g28-gqgq-ghvf","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:59.340Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6c882745c639e2b474fac90ea739d336"],"technology":"@ppa-web-components/ppa-banner","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (bcf0b03540a27943a2afcc26927ce7256d85328bc4fcbc2562f36a88ad75ce8d)\n@ppa-web-components/ppa-banner@1.0.1 is described as a 'Compatibility shim' but ships only two code paths: a no-op Proxy as its main export, and beacon.cjs. beacon.cjs defines BEACON = \"http://185.158.107.175:8787/_ah/dc\" and a fire() function that POSTs a JSON payload containing the package name, os.hostname(), the install path (__dirname), process.cwd(), and the Node/npm version to that bare-IP, plain-HTTP endpoint. fire() is invoked both from the postinstall lifecycle hook (`node beacon.cjs`) and from the module's main entry, so the beacon fires automatically on `npm install` and again whenever the package is required. The destination is an unrelated bare IP over cleartext HTTP, not any publisher-controlled or registry infrastructure, and the shipped stub has no functional purpose other than the beacon. The scoped-name + stub + install-time recon beacon shape is consistent with a dependency-confusion recon callback used to identify internal build environments that resolved this public name.\n\n---\n\nCredit: OpenSSF ([source](https://github.com","public_affected_ranges":["= 2.0.0"]},{"certainty":"source_listed","source_ids":["sr-6c882745c639e2b474fac90ea739d336"],"technology":"@ppa-web-components/ppa-banner","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (bcf0b03540a27943a2afcc26927ce7256d85328bc4fcbc2562f36a88ad75ce8d)\n@ppa-web-components/ppa-banner@1.0.1 is described as a 'Compatibility shim' but ships only two code paths: a no-op Proxy as its main export, and beacon.cjs. beacon.cjs defines BEACON = \"http://185.158.107.175:8787/_ah/dc\" and a fire() function that POSTs a JSON payload containing the package name, os.hostname(), the install path (__dirname), process.cwd(), and the Node/npm version to that bare-IP, plain-HTTP endpoint. fire() is invoked both from the postinstall lifecycle hook (`node beacon.cjs`) and from the module's main entry, so the beacon fires automatically on `npm install` and again whenever the package is required. The destination is an unrelated bare IP over cleartext HTTP, not any publisher-controlled or registry infrastructure, and the shipped stub has no functional purpose other than the beacon. The scoped-name + stub + install-time recon beacon shape is consistent with a dependency-confusion recon callback used to identify internal build environments that resolved this public name.\n\n---\n\nCredit: OpenSSF ([source](https://github.com","public_affected_ranges":["= 2.0.1"]},{"certainty":"source_listed","source_ids":["sr-6c882745c639e2b474fac90ea739d336"],"technology":"@ppa-web-components/ppa-banner","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (bcf0b03540a27943a2afcc26927ce7256d85328bc4fcbc2562f36a88ad75ce8d)\n@ppa-web-components/ppa-banner@1.0.1 is described as a 'Compatibility shim' but ships only two code paths: a no-op Proxy as its main export, and beacon.cjs. beacon.cjs defines BEACON = \"http://185.158.107.175:8787/_ah/dc\" and a fire() function that POSTs a JSON payload containing the package name, os.hostname(), the install path (__dirname), process.cwd(), and the Node/npm version to that bare-IP, plain-HTTP endpoint. fire() is invoked both from the postinstall lifecycle hook (`node beacon.cjs`) and from the module's main entry, so the beacon fires automatically on `npm install` and again whenever the package is required. The destination is an unrelated bare IP over cleartext HTTP, not any publisher-controlled or registry infrastructure, and the shipped stub has no functional purpose other than the beacon. The scoped-name + stub + install-time recon beacon shape is consistent with a dependency-confusion recon callback used to identify internal build environments that resolved this public name.\n\n---\n\nCredit: OpenSSF ([source](https://github.com","public_affected_ranges":["= 1.0.0"]},{"certainty":"source_listed","source_ids":["sr-6c882745c639e2b474fac90ea739d336"],"technology":"@ppa-web-components/ppa-banner","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (bcf0b03540a27943a2afcc26927ce7256d85328bc4fcbc2562f36a88ad75ce8d)\n@ppa-web-components/ppa-banner@1.0.1 is described as a 'Compatibility shim' but ships only two code paths: a no-op Proxy as its main export, and beacon.cjs. beacon.cjs defines BEACON = \"http://185.158.107.175:8787/_ah/dc\" and a fire() function that POSTs a JSON payload containing the package name, os.hostname(), the install path (__dirname), process.cwd(), and the Node/npm version to that bare-IP, plain-HTTP endpoint. fire() is invoked both from the postinstall lifecycle hook (`node beacon.cjs`) and from the module's main entry, so the beacon fires automatically on `npm install` and again whenever the package is required. The destination is an unrelated bare IP over cleartext HTTP, not any publisher-controlled or registry infrastructure, and the shipped stub has no functional purpose other than the beacon. The scoped-name + stub + install-time recon beacon shape is consistent with a dependency-confusion recon callback used to identify internal build environments that resolved this public name.\n\n---\n\nCredit: OpenSSF ([source](https://github.com","public_affected_ranges":["= 1.0.1"]},{"certainty":"source_listed","source_ids":["sr-6c882745c639e2b474fac90ea739d336"],"technology":"@ppa-web-components/ppa-banner","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (bcf0b03540a27943a2afcc26927ce7256d85328bc4fcbc2562f36a88ad75ce8d)\n@ppa-web-components/ppa-banner@1.0.1 is described as a 'Compatibility shim' but ships only two code paths: a no-op Proxy as its main export, and beacon.cjs. beacon.cjs defines BEACON = \"http://185.158.107.175:8787/_ah/dc\" and a fire() function that POSTs a JSON payload containing the package name, os.hostname(), the install path (__dirname), process.cwd(), and the Node/npm version to that bare-IP, plain-HTTP endpoint. fire() is invoked both from the postinstall lifecycle hook (`node beacon.cjs`) and from the module's main entry, so the beacon fires automatically on `npm install` and again whenever the package is required. The destination is an unrelated bare IP over cleartext HTTP, not any publisher-controlled or registry infrastructure, and the shipped stub has no functional purpose other than the beacon. The scoped-name + stub + install-time recon beacon shape is consistent with a dependency-confusion recon callback used to identify internal build environments that resolved this public name.\n\n---\n\nCredit: OpenSSF ([source](https://github.com","public_affected_ranges":["= 0.0.1"]},{"certainty":"source_listed","source_ids":["sr-6c882745c639e2b474fac90ea739d336"],"technology":"@ppa-web-components/ppa-banner","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (bcf0b03540a27943a2afcc26927ce7256d85328bc4fcbc2562f36a88ad75ce8d)\n@ppa-web-components/ppa-banner@1.0.1 is described as a 'Compatibility shim' but ships only two code paths: a no-op Proxy as its main export, and beacon.cjs. beacon.cjs defines BEACON = \"http://185.158.107.175:8787/_ah/dc\" and a fire() function that POSTs a JSON payload containing the package name, os.hostname(), the install path (__dirname), process.cwd(), and the Node/npm version to that bare-IP, plain-HTTP endpoint. fire() is invoked both from the postinstall lifecycle hook (`node beacon.cjs`) and from the module's main entry, so the beacon fires automatically on `npm install` and again whenever the package is required. The destination is an unrelated bare IP over cleartext HTTP, not any publisher-controlled or registry infrastructure, and the shipped stub has no functional purpose other than the beacon. The scoped-name + stub + install-time recon beacon shape is consistent with a dependency-confusion recon callback used to identify internal build environments that resolved this public name.\n\n---\n\nCredit: OpenSSF ([source](https://github.com","public_affected_ranges":["= 1.1.0"]},{"certainty":"source_listed","source_ids":["sr-6c882745c639e2b474fac90ea739d336"],"technology":"@ppa-web-components/ppa-banner","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (bcf0b03540a27943a2afcc26927ce7256d85328bc4fcbc2562f36a88ad75ce8d)\n@ppa-web-components/ppa-banner@1.0.1 is described as a 'Compatibility shim' but ships only two code paths: a no-op Proxy as its main export, and beacon.cjs. beacon.cjs defines BEACON = \"http://185.158.107.175:8787/_ah/dc\" and a fire() function that POSTs a JSON payload containing the package name, os.hostname(), the install path (__dirname), process.cwd(), and the Node/npm version to that bare-IP, plain-HTTP endpoint. fire() is invoked both from the postinstall lifecycle hook (`node beacon.cjs`) and from the module's main entry, so the beacon fires automatically on `npm install` and again whenever the package is required. The destination is an unrelated bare IP over cleartext HTTP, not any publisher-controlled or registry infrastructure, and the shipped stub has no functional purpose other than the beacon. The scoped-name + stub + install-time recon beacon shape is consistent with a dependency-confusion recon callback used to identify internal build environments that resolved this public name.\n\n---\n\nCredit: OpenSSF ([source](https://github.com","public_affected_ranges":["= 3.0.0"]}],"null_published_at":"2026-10-31T22:13:27.100Z","source_updated_at":"2026-10-26T03:30:36.000Z","source_disclosed_at":"2026-10-25T15:31:37.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-31T21:56:59.340Z"}],"next_cursor":null,"snapshot_revision":"42594"}