The remote recipient learns identifying details about the installing machine and project without an installer consent guard.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
Source confirms an unguarded postinstall beacon that sends identifying host and project metadata to a fixed external endpoint. This is automatic installation tracking without installer consent, supporting a malicious install-hook verdict.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation or importing index.js.
Mechanism
The postinstall script runs beacon.cjs, which sends a JSON POST containing the hostname, installation path, working directory, and package metadata.
Attack narrative
The postinstall hook automatically sends machine and project identifiers to a fixed external IP address. The package import path invokes the same beacon. No installer consent check appears in the inspected execution path; this supports blocking as an installation-time disclosure.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The postinstall hook automatically runs the beacon during installation.
The beacon sends a POST to a fixed external IP address.
The request includes the machine hostname, installation path, and working directory.
Importing the package also invokes the beacon.
Evidence against
The inspected payload contains machine and package metadata; no credential collection is shown.
Behavioral surface
SourceNetwork
Supply chainURL strings
ManifestNo manifest risk signals triggered.
Scanned 2 files · 2.30 KB of source
1 external domain referenced
185.158.107.175
Findings
8 high · 1 medium · 2 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
Avoid installing @ppa-web-components/ppa-builder@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.