GHSA-5q5w-4m9f-ppmg: Malicious code in @ppa-web-components/ppa-builder (npm)

Published Oct 25, 2026
·
Updated

@ppa-web-components/ppa-builder is a dependency-confusion package: it is described as a "Compatibility shim", uses inflated version numbers, and its README calls it an "authorized dependency-confusion test". Each listed version (0.0.1, 1.0.0, 1.0.1, 99.0.1, 2.0.1, 3.0.0) has a postinstall script that runs node beacon.cjs on npm install, and index.js calls the same code when the package is imported; it POSTs the hostname, install path and current working directory over plain HTTP to http://185.158.107.175:8787/ah/dc, and index.js exports a Proxy that returns no-op functions so builds importing the real package keep running. The npm account wiseke published 14 such packages under the @greenlake, @sxm-web, @drone-js-ext and @ppa-web-components scopes between 2026-10-23 21:23 and 2026-10-25 14:28 UTC; index.js is byte-identical to that of ph-common (MAL-2026-1809), which sends to the same endpoint.

--- -= Per source details. Do not edit below this line.=-

Source: amazon-inspector (cc4615498b50aa4b5f39a8367c44e6a18d4a7272ae71235716a152b2933d5ddd) The package is described as a 'Compatibility shim' and ships a stub Proxy-based main plus beacon.cjs. The package.json declares scripts.postinstall: 'node beacon.cjs', and the main entry also invokes the same fire() routine on require. On both triggers, beacon.cjs collects installer identifiers — os.hostname(), dirname (install path), process.cwd(), process.version, and the package name — and POSTs them in cleartext to the hardcoded bare-IP endpoint http://185.158.107.175:8787/ah/dc. The destination is not a registry, publisher, or any documented infrastructure; it is a plain-HTTP bare IP with no TLS. An inline source comment states that a build that completes and calls back is cleaner evidence, confirming the artifact's purpose is to signal successful resolution and execution on installer machines. Combined with a scoped name resembling an internal namespace and no real library functionality, this matches the dependency-confusion / namesquat callback-probe shape.

Source: ghsa-malware (25f793f86454c72ad9c76b0ef0948c16f82bc42fb58d8d9f8e68224e52eb92fd) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Affected Software

2 affected components
npm/@ppa-web-components/ppa-builder*
npm/@ppa-web-components/ppa-builder>=0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove @ppa-web-components/ppa-builder from your environment.

    Remove the package from any computer where it is installed.

  2. Operational

    Rotate all secrets and keys stored on any computer where @ppa-web-components/ppa-builder was installed or running, immediately and from a different computer.

Event History

Oct 25, 2026
Advisory Published
via OSV·02:22 PM
Data Sourced
via OSV·02:22 PM
DescriptionAffected Software
Oct 26, 2026
Advisory Published
via GitHub·04:27 PM
Data Sourced
via GitHub·04:27 PM
DescriptionWeaknessAffected Software

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203