The recipient can learn the installing machine's host name and identify its package and project locations.
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 automatic lifecycle hook and import path transmit identifying host and project metadata to a fixed external collector without consent. This supports blocking as an installation beacon.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation or import of index.js.
Mechanism
The postinstall hook runs beacon.cjs, which sends a POST containing the host name, install path, and working directory to a fixed IP address; index.js invokes the same beacon on import.
Attack narrative
On installation, the package runs a beacon that sends host and project identifying metadata to a fixed external IP without an installer consent check. Importing the package entrypoint triggers the same transmission.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
package.json runs beacon.cjs automatically after installation.
beacon.cjs posts machine and package metadata to a fixed external IP without a consent check.
The posted payload includes the host name, install path, and working directory.
Importing index.js also calls the beacon.
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
8 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.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.