The endpoint receives identifying information about the installing machine and project location.
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 postinstall hook causes an automatic external disclosure of host and project-location identifiers without an installer consent guard. The package entrypoint also triggers the beacon when imported.
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 hook; importing index.js is another trigger.
Mechanism
beacon.cjs creates a payload with the hostname, installation path, working directory, and runtime metadata, then sends it in an HTTP POST.
Attack narrative
Installing the package automatically runs a beacon that sends the machine hostname and package location to a fixed external endpoint. Importing the package triggers the same send.
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 during postinstall.
beacon.cjs selects a fixed HTTP endpoint and builds a POST request to it.
The request body includes the machine hostname, installation path, and working directory.
The beacon writes the payload to the request and completes the send.
Importing index.js also fires the beacon.
Evidence against
Behavioral surface
SourceNetwork
Supply chainURL strings
ManifestNo manifest risk signals triggered.
Scanned 2 files · 2.29 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 @sxm-web/client-sdk-core@1.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.