The recipient can correlate package installations with hostnames and local installation paths.
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 installation beacon that discloses host and installation identifiers to a fixed external collector without consent. This meets the installation beacon blocking policy.
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 constructs a metadata payload and sends it in an HTTP POST without a consent check.
Attack narrative
The postinstall hook invokes the beacon, and the package entrypoint invokes it again on import. The beacon sends the host name, package installation path, working directory, and npm/Node version to a fixed external IP without installer consent.
Evidence
package.jsonindex.jsbeacon.cjs
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
package.json runs beacon.cjs automatically during postinstall.
index.js also fires the beacon when the package is imported.
beacon.cjs sends a POST to a fixed external IP address.
The payload includes the machine hostname, install path, working directory, and npm/Node version, with no consent guard.
Evidence against
Behavioral surface
SourceNetwork
Supply chainURL strings
ManifestNo manifest risk signals triggered.
Scanned 2 files · 2.29 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-banner@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.