At runtime, an application calling provider(serverUrl) establishes a WebSocket control channel. The hidden logic can start a platform shell and exchange command/output messages with that server.
Static reason
No blocking static signals were detected.
Trigger
Application imports the package and calls provider(serverUrl).
Impact
A supplied or compromised control server can execute arbitrary OS commands with the host process's privileges.
Mechanism
Obfuscated WebSocket-controlled shell execution.
Attack narrative
The exported provider function activates an obfuscated virtual-machine payload. Its embedded strings and control flow show registration to the supplied server, WebSocket command handling, platform shell spawning (cmd.exe or /bin/bash), and output/acknowledgement relay. This creates a remote-command channel not justified by the advertised health-monitoring API.
Rationale
Although activation is user-invoked rather than install-time, the package conceals a remote shell behind a health-client interface. The concrete command-and-control behavior warrants blocking.
Evidence
package.jsonindex.jsREADME.mdindex.d.ts