@ppa-web-components/ppa-builder@3.0.0
Malicious code in @ppa-web-components/ppa-builder (npm)
Analysis
The package's package.json postinstall hook runs beacon.cjs, and index.js also invokes the same beacon when the module is required, so installing or importing the package triggers a callback. beacon.cjs POSTs a JSON body containing the package name, the machine hostname, the install path (__dirname), the working directory, the npm/node user agent and the protocol to hxxp://185[.]158[.]107[.]175:8787/_ah/dc, with an X-Beacon-Package header naming the package. The package is a compatibility shim that exports a no-op Proxy, so the callback is the only behaviour it performs. It collects no environment values, credentials, tokens or file contents.
- analyzed by
- Leitwacht
- first seen
- Oct 25, 2026, 10:53 PM
- analyzed
- Oct 25, 2026, 10:55 PM
Related advisories
- @ppa-web-components/ppa-builder@2.0.1 same package
- @ppa-web-components/ppa-builder@1.0.1 same package
- @ppa-web-components/ppa-builder@1.0.0 same package
- @ppa-web-components/ppa-banner@3.0.0
- @drone-js-ext/core@2.0.1
- @drone-js-ext/vip-badge@0.1.0
- @drone-js-ext/vip-badge@0.0.1
- @drone-js-ext/vip-badge@2.0.0
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.