The external recipient can learn identifying information about the installing machine and project without installer consent.
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 identifiers to a fixed external endpoint. This supports blocking the package 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 importing index.js.
Mechanism
beacon.cjs collects the hostname, install path, working directory, and npm version, then sends them by HTTP POST to 185.158.107.175:8787.
Attack narrative
The postinstall hook runs beacon.cjs, which sends host and project identifying metadata to a hard-coded external IP address without a consent gate. The package entry point also fires the beacon when imported, extending the disclosure beyond installation.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The package runs beacon.cjs automatically during installation.
The beacon sends a POST request to a hard-coded external IP address.
The request payload includes the machine hostname, install path, working directory, and npm version, with no consent check.
Importing the package entry point also fires 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
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-searchform@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.