The endpoint 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
Source confirms automatic install-time disclosure of host and installation identifiers to a fixed external collector without installer consent. This supports blocking the package as data exfiltration.
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
beacon.cjs collects host and install metadata and sends it in an HTTP POST request without a consent check.
Attack narrative
The postinstall hook runs beacon.cjs automatically. That file gathers the machine hostname and package install context, then posts the data to a fixed external IP without a consent check. The package entry point independently calls the same 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 package runs beacon.cjs automatically during postinstall.
The beacon sends a POST request to a fixed external IP address without a consent check.
The payload includes the machine hostname, install path, working directory, and npm user agent.
Importing the package entry point 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@2.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.