The collector receives host and project environment details without installer consent.
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 manifest activates a beacon during installation, and the beacon sends host and installation metadata to a fixed external address. This matches unconsented installation-time disclosure behavior.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
The package's postinstall script runs the beacon.
Mechanism
The beacon sends an HTTP request containing the hostname, install path, working directory, and runtime version to a fixed external address.
Attack narrative
During installation, the postinstall hook runs a beacon that sends the machine hostname, package installation path, working directory, and runtime version to a fixed external collector. This is automatic installation-time disclosure of identifying environment data without an installer consent guard.
Evidence
package.jsonbeacon.cjs
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The package manifest runs the beacon during installation.
The beacon sends a request to a fixed external address and includes machine and installation metadata in its payload.
The beacon sends that payload when run as the main script.
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
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-navigation@3.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.