The collector receives identifying information about the machine and package installation.
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
The postinstall hook activates a fixed-endpoint beacon that transmits host and installation metadata without a shown consent guard. This supports blocking for concrete data exfiltration, although the inspected payload does not show credential collection.
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 beacon constructs a JSON payload with host and directory information and sends it by HTTP POST to a fixed address without a shown consent check.
Attack narrative
The postinstall hook runs the beacon automatically. It sends the hostname, install path, and current directory to a fixed external address, and importing the package entry point also invokes the beacon. This is unconsented installation-time disclosure of host and project metadata.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The package runs beacon.cjs automatically during postinstall.
The beacon sends a POST request to a fixed external address.
The payload includes the machine hostname, install path, and current directory.
The beacon writes the payload to the request body.
Importing index.js also invokes the beacon.
Evidence against
The inspected payload contains host 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
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@99.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.