The remote recipient receives identifiers 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 confirms unconsented installation-time disclosure of machine and installation identifiers to a fixed external collector. This supports blocking under the installation beacon policy.
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.
Mechanism
The beacon gathers the hostname, installation path, working directory, and npm version, then posts them to the configured endpoint without a consent check.
Attack narrative
The postinstall hook runs the beacon automatically. The beacon collects machine and installation identifiers and posts them to a fixed external IP address without an evident consent guard. The package entry point also fires the beacon when imported.
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 collects the machine hostname, installation path, working directory, and npm version.
It sends the collected data by POST to a fixed external IP address.
Importing the package also fires the beacon automatically.
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@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.