The remote recipient receives machine and installation identifiers 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 inspection confirms automatic disclosure of machine and installation identifiers to an unrelated hardcoded endpoint. This is an install-time data disclosure attack, so publishing should be blocked.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
The package's postinstall hook runs, or a consumer imports index.js.
Mechanism
The beacon posts a payload containing the hostname and local install path over plain HTTP without a consent check.
Attack narrative
The postinstall hook runs the beacon automatically, and importing the package also invokes it. The beacon sends the machine hostname and local install path to a hardcoded external IP over plain HTTP without a consent check.
Evidence
package.jsonindex.jsbeacon.cjs
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The package manifest runs beacon.cjs automatically after installation.
Importing index.js also calls the beacon, so the disclosure can happen during package use.
The beacon sends a POST to a hardcoded external IP address over plain HTTP.
The transmitted payload includes the machine hostname and local install path.
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@3.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.