The external recipient learns identifying details about the machine and package installation 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 the beacon during installation, and beacon.cjs sends host and installation identifiers to a fixed external endpoint. This is unconsented installation-time disclosure, so publication should be blocked.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Installing the package runs its postinstall hook.
Mechanism
The hook constructs a payload containing the hostname, install path, working directory, and npm version, then posts it to the configured IP address.
Attack narrative
Installing the package triggers a postinstall script that sends the machine hostname, install path, working directory, and npm version to a fixed external IP address. The source shows no installer consent gate for this disclosure.
Evidence
package.jsonbeacon.cjs
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
package.json runs beacon.cjs from an automatic postinstall hook.
beacon.cjs selects a fixed external HTTP endpoint.
beacon.cjs collects the hostname, install path, working directory, and npm version.
beacon.cjs sends the serialized payload in an HTTP request.
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
7 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.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.