T08 · Insecure Dependencies
- Location
skill.md:112- Finding
Unpinned Third-Party Dependencies Handle Wallet Keys and Financial Transactions
- Content
View full analysis
- Remediation
View remediation
npm install --save-exact @pakt/psilo@ npm install --save-exact @buildersgarden/siwa@ ``` 2. Provide and enforce a reviewed lockfile using `npm ci` rather than unconstrained `npm install`. 3. Verify package provenance, publisher identity, signatures or attestations, and registry integrity metadata. 4. Audit direct and transitive dependencies before upgrades. Treat wallet and signing package updates as security-sensitive changes requiring renewed review. 5. Disable installation scripts where operationally possible, for example with `npm ci --ignore-scripts`, after confirming required package behavior. 6. Run wallet and transaction preparation components with minimal filesystem and environment access. 7. Keep signing isolated from network-facing SDK code. Before signing, independently decode and verify the chain ID, target contract, function selector, recipient, token, amount, nonce, and value. 8. Require explicit user approval for the final decoded transaction rather than trusting the SDK's prepared payload. 9. Protect wallet files with strict filesystem permissions and avoid exposing unrelated secrets to the signing process. ]]>
