The recipient receives identifying details about the machine and package installation without an affirmative consent guard in the sending path.
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 inspection confirms automatic install-time disclosure of host and package-install identifiers to a hardcoded external IP, with no affirmative consent guard. This supports blocking the package as an installation beacon.
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
beacon.cjs builds a payload with the package name, hostname, install path, working directory, and npm version, then sends it in an HTTP POST.
Attack narrative
During postinstall, the package runs beacon.cjs, which sends hostname, install path, working directory, package name, and npm version to a hardcoded external endpoint. Importing the main entrypoint also calls the beacon. The source shows no affirmative consent guard on either path.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
package.json runs the beacon automatically during postinstall.
beacon.cjs sends machine and install metadata to a hardcoded external endpoint.
Importing index.js also fires the beacon.
Evidence against
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
9 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@2.0.1. 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.