{"items":[{"id":"NVI-00008425","kind":"supply_chain_event","title":"Malicious code in @ppa-web-components/ppa-headerfooter (npm)","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-vhvr-f5ww-qh72"],"plain_summary":"GitHub lists this malware advisory for @ppa-web-components/ppa-headerfooter, @ppa-web-components/ppa-headerfooter, @ppa-web-components/ppa-headerfooter, @ppa-web-components/ppa-headerfooter, @ppa-web-components/ppa-headerfooter. 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-26f63fdbf6ea7e60df4cec39466dc905"],"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-26f63fdbf6ea7e60df4cec39466dc905","url":"https://github.com/advisories/GHSA-vhvr-f5ww-qh72","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-vhvr-f5ww-qh72","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:59.340Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-26f63fdbf6ea7e60df4cec39466dc905"],"technology":"@ppa-web-components/ppa-headerfooter","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (32234bc8ba0c918d154d680b15a1bcb7ae6f6b7d20365c02095842b84e245dce)\nThe package ships a `beacon.cjs` script wired as both the `postinstall` lifecycle hook (`node beacon.cjs`) and a require-time side effect from `index.js`. On install and on `require()`, the beacon POSTs installer identifiers — `os.hostname()`, the install path (`__dirname`), `process.cwd()`, `process.version`, and the package name — to the hardcoded bare-IP plaintext HTTP endpoint `http://185.158.107.175:8787/_ah/dc`. The package otherwise provides no functionality: `index.js` exports a Proxy that returns a no-op function for every property access, so the beacon is the sole purpose of the package. The combination of a scoped name resembling a web-components namespace, a 'Compatibility shim' description, a functionless Proxy stub, and a bare-IP recon beacon is the shape of a dependency-confusion / typosquat probe measuring where the package resolves inside private build environments, typically preceding a targeted follow-up payload.\n\n---\n\nCredit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/f1b566fc7d6dea647e412d6b49df4b5bd","public_affected_ranges":["= 1.0.1"]},{"certainty":"source_listed","source_ids":["sr-26f63fdbf6ea7e60df4cec39466dc905"],"technology":"@ppa-web-components/ppa-headerfooter","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (32234bc8ba0c918d154d680b15a1bcb7ae6f6b7d20365c02095842b84e245dce)\nThe package ships a `beacon.cjs` script wired as both the `postinstall` lifecycle hook (`node beacon.cjs`) and a require-time side effect from `index.js`. On install and on `require()`, the beacon POSTs installer identifiers — `os.hostname()`, the install path (`__dirname`), `process.cwd()`, `process.version`, and the package name — to the hardcoded bare-IP plaintext HTTP endpoint `http://185.158.107.175:8787/_ah/dc`. The package otherwise provides no functionality: `index.js` exports a Proxy that returns a no-op function for every property access, so the beacon is the sole purpose of the package. The combination of a scoped name resembling a web-components namespace, a 'Compatibility shim' description, a functionless Proxy stub, and a bare-IP recon beacon is the shape of a dependency-confusion / typosquat probe measuring where the package resolves inside private build environments, typically preceding a targeted follow-up payload.\n\n---\n\nCredit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/f1b566fc7d6dea647e412d6b49df4b5bd","public_affected_ranges":["= 2.0.1"]},{"certainty":"source_listed","source_ids":["sr-26f63fdbf6ea7e60df4cec39466dc905"],"technology":"@ppa-web-components/ppa-headerfooter","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (32234bc8ba0c918d154d680b15a1bcb7ae6f6b7d20365c02095842b84e245dce)\nThe package ships a `beacon.cjs` script wired as both the `postinstall` lifecycle hook (`node beacon.cjs`) and a require-time side effect from `index.js`. On install and on `require()`, the beacon POSTs installer identifiers — `os.hostname()`, the install path (`__dirname`), `process.cwd()`, `process.version`, and the package name — to the hardcoded bare-IP plaintext HTTP endpoint `http://185.158.107.175:8787/_ah/dc`. The package otherwise provides no functionality: `index.js` exports a Proxy that returns a no-op function for every property access, so the beacon is the sole purpose of the package. The combination of a scoped name resembling a web-components namespace, a 'Compatibility shim' description, a functionless Proxy stub, and a bare-IP recon beacon is the shape of a dependency-confusion / typosquat probe measuring where the package resolves inside private build environments, typically preceding a targeted follow-up payload.\n\n---\n\nCredit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/f1b566fc7d6dea647e412d6b49df4b5bd","public_affected_ranges":["= 1.1.0"]},{"certainty":"source_listed","source_ids":["sr-26f63fdbf6ea7e60df4cec39466dc905"],"technology":"@ppa-web-components/ppa-headerfooter","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (32234bc8ba0c918d154d680b15a1bcb7ae6f6b7d20365c02095842b84e245dce)\nThe package ships a `beacon.cjs` script wired as both the `postinstall` lifecycle hook (`node beacon.cjs`) and a require-time side effect from `index.js`. On install and on `require()`, the beacon POSTs installer identifiers — `os.hostname()`, the install path (`__dirname`), `process.cwd()`, `process.version`, and the package name — to the hardcoded bare-IP plaintext HTTP endpoint `http://185.158.107.175:8787/_ah/dc`. The package otherwise provides no functionality: `index.js` exports a Proxy that returns a no-op function for every property access, so the beacon is the sole purpose of the package. The combination of a scoped name resembling a web-components namespace, a 'Compatibility shim' description, a functionless Proxy stub, and a bare-IP recon beacon is the shape of a dependency-confusion / typosquat probe measuring where the package resolves inside private build environments, typically preceding a targeted follow-up payload.\n\n---\n\nCredit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/f1b566fc7d6dea647e412d6b49df4b5bd","public_affected_ranges":["= 99.0.1"]},{"certainty":"source_listed","source_ids":["sr-26f63fdbf6ea7e60df4cec39466dc905"],"technology":"@ppa-web-components/ppa-headerfooter","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (32234bc8ba0c918d154d680b15a1bcb7ae6f6b7d20365c02095842b84e245dce)\nThe package ships a `beacon.cjs` script wired as both the `postinstall` lifecycle hook (`node beacon.cjs`) and a require-time side effect from `index.js`. On install and on `require()`, the beacon POSTs installer identifiers — `os.hostname()`, the install path (`__dirname`), `process.cwd()`, `process.version`, and the package name — to the hardcoded bare-IP plaintext HTTP endpoint `http://185.158.107.175:8787/_ah/dc`. The package otherwise provides no functionality: `index.js` exports a Proxy that returns a no-op function for every property access, so the beacon is the sole purpose of the package. The combination of a scoped name resembling a web-components namespace, a 'Compatibility shim' description, a functionless Proxy stub, and a bare-IP recon beacon is the shape of a dependency-confusion / typosquat probe measuring where the package resolves inside private build environments, typically preceding a targeted follow-up payload.\n\n---\n\nCredit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/f1b566fc7d6dea647e412d6b49df4b5bd","public_affected_ranges":["= 2.0.0"]},{"certainty":"source_listed","source_ids":["sr-26f63fdbf6ea7e60df4cec39466dc905"],"technology":"@ppa-web-components/ppa-headerfooter","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (32234bc8ba0c918d154d680b15a1bcb7ae6f6b7d20365c02095842b84e245dce)\nThe package ships a `beacon.cjs` script wired as both the `postinstall` lifecycle hook (`node beacon.cjs`) and a require-time side effect from `index.js`. On install and on `require()`, the beacon POSTs installer identifiers — `os.hostname()`, the install path (`__dirname`), `process.cwd()`, `process.version`, and the package name — to the hardcoded bare-IP plaintext HTTP endpoint `http://185.158.107.175:8787/_ah/dc`. The package otherwise provides no functionality: `index.js` exports a Proxy that returns a no-op function for every property access, so the beacon is the sole purpose of the package. The combination of a scoped name resembling a web-components namespace, a 'Compatibility shim' description, a functionless Proxy stub, and a bare-IP recon beacon is the shape of a dependency-confusion / typosquat probe measuring where the package resolves inside private build environments, typically preceding a targeted follow-up payload.\n\n---\n\nCredit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/f1b566fc7d6dea647e412d6b49df4b5bd","public_affected_ranges":["= 3.0.0"]},{"certainty":"source_listed","source_ids":["sr-26f63fdbf6ea7e60df4cec39466dc905"],"technology":"@ppa-web-components/ppa-headerfooter","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (32234bc8ba0c918d154d680b15a1bcb7ae6f6b7d20365c02095842b84e245dce)\nThe package ships a `beacon.cjs` script wired as both the `postinstall` lifecycle hook (`node beacon.cjs`) and a require-time side effect from `index.js`. On install and on `require()`, the beacon POSTs installer identifiers — `os.hostname()`, the install path (`__dirname`), `process.cwd()`, `process.version`, and the package name — to the hardcoded bare-IP plaintext HTTP endpoint `http://185.158.107.175:8787/_ah/dc`. The package otherwise provides no functionality: `index.js` exports a Proxy that returns a no-op function for every property access, so the beacon is the sole purpose of the package. The combination of a scoped name resembling a web-components namespace, a 'Compatibility shim' description, a functionless Proxy stub, and a bare-IP recon beacon is the shape of a dependency-confusion / typosquat probe measuring where the package resolves inside private build environments, typically preceding a targeted follow-up payload.\n\n---\n\nCredit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/f1b566fc7d6dea647e412d6b49df4b5bd","public_affected_ranges":["= 1.0.0"]}],"null_published_at":"2026-10-31T22:13:22.845Z","source_updated_at":"2026-10-26T03:30:36.000Z","source_disclosed_at":"2026-10-25T15:31:38.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"}