The external recipient can identify the machine and installation context.
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 installation and import-time disclosure of machine and project identifiers to a fixed external recipient without an affirmative consent guard. This meets the installation beacon policy for blocking.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation or package import.
Mechanism
The beacon gathers the machine hostname, installation path, working directory, and runtime version, then sends them in an HTTP request without an affirmative consent check.
Attack narrative
The postinstall hook runs the beacon automatically. It sends machine and project identifying data to a fixed external address, and importing the package independently triggers the same beacon. No consent guard appears on these paths.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The package runs a beacon script automatically during installation.
The beacon sends an HTTP request to a fixed external address.
The request contains the machine hostname, install path, working directory, and runtime version.
Importing the package 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
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@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.