The recipient receives identifying host and project-location information.
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 automatic, unconsented disclosure of host and project-context identifiers to a hardcoded external recipient. This is active installation-time data exfiltration, so publication should be blocked.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation runs the postinstall hook; importing the package entry point also fires the beacon.
Mechanism
beacon.cjs posts the hostname, install path, working directory, and npm version to the configured endpoint without a consent guard.
Attack narrative
Installation or import triggers an unguarded request to a hardcoded external endpoint. The request includes the host name and local install and working-directory paths, disclosing identifying environment information.
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 from its postinstall hook.
beacon.cjs sends a POST request to a hardcoded external IP address.
The request includes the machine hostname, install path, working directory, and npm version.
Importing index.js also calls the beacon without a consent check.
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
7 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.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.