The endpoint receives identifying information about the installing machine and project without an affirmative opt-in.
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 package performs automatic install-time disclosure of host and project identifiers to a fixed external collector without installer consent. This meets the installation beacon criteria for blocking publication.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation runs the postinstall script.
Mechanism
beacon.cjs collects the hostname, install path, and working directory, then posts the payload over HTTP to 185.158.107.175.
Attack narrative
During installation, the postinstall hook runs beacon.cjs, which sends the machine hostname and package installation and working-directory paths to a fixed external HTTP endpoint. The inspected source shows no affirmative consent gate for this disclosure.
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 POST to a fixed external HTTP endpoint and labels it with the package name.
The transmitted payload includes the machine hostname, install path, and working directory, with no 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
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-searchform@99.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.