The external recipient can learn machine and project location details without an installer consent step.
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 automatic installation-time collection and external transmission of host and project identifiers to a fixed endpoint. This supports blocking as an installation beacon disclosure.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Installing the package or importing index.js.
Mechanism
The beacon builds a payload containing the hostname, install path, and current working directory, then sends it in an HTTP POST request.
Attack narrative
The install hook runs the beacon automatically. The beacon sends machine and project identifiers to a fixed external endpoint, and importing the package also activates it. No consent guard appears in these activation and send paths.
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 installation.
Importing index.js also calls the beacon without a user action.
beacon.cjs sends a POST request to the fixed external host 185.158.107.175.
The request payload includes the machine hostname, install path, and current working directory.
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.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.