The collector receives identifying information about the machine and package installation environment.
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 postinstall execution and transmission of host and installation metadata to a hardcoded external collector. This unconsented installation beacon warrants blocking publication.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
The package's postinstall hook runs beacon.cjs.
Mechanism
The beacon builds a JSON payload with host and install metadata, then sends it by HTTP POST to a hardcoded IP address.
Attack narrative
The postinstall hook automatically launches a beacon that sends the machine name, install path, working directory, and npm runtime version to a fixed external endpoint. This is installation-time disclosure without an evident consent gate.
Evidence
package.jsonbeacon.cjs
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshot
Evidence for block
The package runs beacon.cjs automatically in its postinstall hook.
beacon.cjs sends a POST to a fixed external IP address over HTTP.
The submitted payload includes the machine name, install path, working directory, and npm runtime version.
Running beacon.cjs directly fires the beacon without a consent check.
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@13.3.7. 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.