The remote recipient learns the host name and local installation and working-directory paths, along with npm version information.
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 automatically during installation, and the source shows a hardcoded external recipient and host-identifying metadata in the request. This unconsented installation beacon warrants blocking publication.
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 posts a JSON payload containing machine and package installation metadata to the configured HTTP endpoint.
Attack narrative
During installation, the package's postinstall hook runs beacon.cjs, which sends the host name, installation path, working directory, and npm version to a hardcoded external HTTP endpoint. The source shows no installer consent check. This is automatic installation-time disclosure of identifying host and path information.
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 automatically during postinstall.
beacon.cjs sends a JSON POST to a hardcoded external HTTP address.
The payload includes the machine name, install path, working directory, and npm version, with no installer consent check.
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-headerfooter@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.