The recipient receives machine identity and local filesystem path information 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
Source confirms an automatic install-time beacon that discloses host and project-path identifiers to a hardcoded external endpoint without consent. This supports blocking the package for data exfiltration.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
npm postinstall runs beacon.cjs; importing index.js calls the same beacon.
Mechanism
The beacon sends a JSON HTTP POST containing the hostname, install path, working directory, package name, and npm protocol metadata to a hardcoded IP address. No consent gate appears on these paths.
Attack narrative
The postinstall hook runs the beacon automatically. It posts the machine hostname and local install and working-directory paths to a hardcoded external IP address without an opt-in check. Importing the package entrypoint also fires the beacon. This is unconsented installation-time disclosure of identifying environment data.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
package.json runs beacon.cjs during postinstall.
beacon.cjs sends an HTTP POST to a hardcoded external IP address.
The beacon payload includes the machine hostname and local install and working-directory paths.
index.js calls the beacon when imported, with no consent check on either path.
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
9 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@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.