Summary
Togoder Security scanned the npm package @scure/bip32@1.4.0 on Oct 4, 2026. An AI review of 3 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| index.ts | safe | No malicious patterns detected; the code is a legitimate BIP32 HD key implementation with standard cryptographic operations. |
| lib/esm/index.js | safe | No malicious patterns detected; the code is a legitimate BIP32 HD key implementation for Bitcoin with no exfiltration, obfuscation, or suspicious behavior. |
| lib/index.js | safe | This is a legitimate implementation of BIP32 hierarchical deterministic keys from the scure-bip32 library with no malicious patterns detected. |
Affected version ranges
None of the 3 scanned versions of @scure/bip32 are flagged high or critical. The latest scanned version, 1.7.0, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of @scure/bip32
Frequently asked questions
Is @scure/bip32 safe to use?
Our AI source review of @scure/bip32@1.4.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @scure/bip32 contain malware?
No malware was identified in @scure/bip32@1.4.0 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was @scure/bip32 checked?
Togoder Security downloaded the published npm package and had an AI model read its 3 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan @scure/bip32 together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in @scure/bip32@1.4.0, cost nothing.