Installation and environment identifiers are disclosed to the endpoint.
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 package performs unconsented install-time disclosure of host and installation metadata to a fixed external endpoint. This supports blocking as install hook abuse.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation runs the postinstall script; importing index.js also invokes the beacon.
Mechanism
The beacon builds a payload containing the hostname, install path, working directory, npm user-agent, and protocol, then sends it in an HTTP POST request.
Attack narrative
Installing the package automatically runs beacon.cjs, which sends machine and package installation metadata to a fixed external endpoint without a consent check. Importing index.js also invokes the same beacon.
Evidence
package.jsonindex.jsbeacon.cjs
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The postinstall script runs beacon.cjs automatically.
Importing index.js also calls the beacon function.
The beacon uses a fixed HTTP endpoint.
The beacon sends a POST request.
The payload includes the machine hostname, install path, and working directory.
The beacon function passes the payload to the request sender.
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-headerfooter@3.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.