Discloses identifying machine and project-location metadata to the endpoint without an indicated consent guard.
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-time disclosure of host and package-location metadata to a fixed external endpoint. This is an active installation beacon, so the package 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 or package import.
Mechanism
The beacon collects the hostname, installation path, and working directory, then sends them in an HTTP POST to a hardcoded IP address.
Attack narrative
The package's postinstall command runs the beacon automatically. The beacon sends the machine hostname and installation and working directory paths to a hardcoded external IP address. The package entrypoint also invokes the beacon when imported.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The postinstall hook runs the beacon automatically when the package is installed.
The beacon sends an HTTP POST to a fixed external IP address.
The POST payload includes the machine hostname and installation and working directory paths.
Importing the package also calls 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@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.