The endpoint receives identifying machine and installation metadata without an evident installer consent guard.
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 automatic install-time disclosure of host and installation identifiers to a hardcoded external collector without an installer consent guard. This supports blocking as an installation beacon attack.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation or importing index.js.
Mechanism
The postinstall script runs beacon.cjs, which sends a JSON POST containing the hostname, install path, working directory, and npm version to the fixed endpoint.
Attack narrative
The package's postinstall hook automatically runs beacon.cjs. That file sends host and installation identifiers to a hardcoded external IP address, with no consent check evident in the inspected path. The main entrypoint independently fires the same beacon when imported.
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 after installation.
beacon.cjs sends a POST to a hardcoded external IP address.
The posted metadata includes the machine hostname, install path, working directory, and npm version.
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
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@2.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.