An external recipient receives identifying information about the machine and package installation.
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, unconsented installation-time disclosure of host and project identifiers to a fixed external recipient. This supports blocking as installation beacon exfiltration.
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 the main entrypoint.
Mechanism
The beacon posts the hostname, install path, working directory, and npm version without an effective consent check.
Attack narrative
During installation, `postinstall` runs the beacon, which sends the machine hostname, installation path, working directory, and npm version to a fixed external IP. Importing the main entrypoint also fires the beacon. The source shows no consent guard for either trigger.
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 `postinstall`.
The beacon sends the machine hostname, installation path, working directory, and npm version to a fixed external IP without a consent guard.
Importing the main entrypoint 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
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 @sxm-web/client-sdk-core@1.1.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.