The postinstall hook downloads and executes a native binary, and its default proxy can supply both the binary and its validating checksum. The package intends to retrieve its own release asset and has safeguards, but the checksum is not independently anchored, leaving a meaningful installation-time supply-chain risk.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Automatic postinstall execution.
Impact
A compromised or malicious default proxy could cause attacker-controlled native code to execute during installation.
Mechanism
The hook fetches SHA256SUMS and the native binary through the same proxy candidate list. A proxy that alters both responses can provide a matching digest for an altered binary, which the hook then installs and loads.
Evidence
package.jsonpostinstall.jsnative/jsql-neo-native.node