Discloses machine identity and local installation context to an unrelated fixed recipient.
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 unconsented install-time disclosure of host and project context to a fixed external endpoint, with an additional import-time trigger. This is concrete data exfiltration behavior and warrants blocking publication.
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 builds a JSON payload from the hostname, install path, working directory, and npm version, then sends it in an HTTP POST to 185.158.107.175.
Attack narrative
Installation automatically runs a reporter that sends the machine hostname and local install context to a fixed external IP. The package entrypoint also invokes the reporter when imported, so the disclosure is not limited to installation.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The package postinstall hook runs the beacon script automatically.
The reporter targets a fixed external IP and sends a POST request with package identification.
The request body includes the machine hostname, install path, working directory, and npm version.
The beacon sends the serialized payload, and importing the package entrypoint also invokes it.
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@1.1.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.