Summary
Togoder Security scanned the npm package @scure/bip39@1.3.0 on Oct 4, 2026. An AI review of 23 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 |
|---|---|---|
| esm/index.js | safe | No malicious patterns detected |
| esm/wordlists/czech.js | safe | No malicious patterns detected |
| esm/wordlists/english.js | safe | No malicious patterns detected; the file only exports a static list of English words with no network, filesystem, process, or dynamic code execution behavior. |
| esm/wordlists/french.js | safe | No malicious patterns detected |
| esm/wordlists/italian.js | safe | This file contains only a static exported array of Italian words with no executable code, network calls, or other malicious patterns. |
| esm/wordlists/japanese.js | safe | No malicious patterns detected |
| esm/wordlists/korean.js | safe | No malicious patterns detected |
| esm/wordlists/portuguese.js | safe | The file contains only a hardcoded Portuguese wordlist and no executable or malicious code. |
| esm/wordlists/simplified-chinese.js | safe | The file contains only a static list of Simplified Chinese words with no executable code or malicious patterns. |
| esm/wordlists/spanish.js | safe | This file contains only a static Spanish wordlist with no executable code, network requests, or other malicious patterns. |
| esm/wordlists/traditional-chinese.js | safe | No malicious patterns detected; the file contains only a static string list of common Chinese characters used as a wordlist. |
| index.js | safe | The code is a legitimate implementation of BIP39 mnemonic generation and seed derivation using well-known cryptographic libraries, with no malicious patterns detected. |
| src/index.ts | safe | No malicious patterns detected |
| wordlists/czech.js | safe | No malicious patterns detected |
| wordlists/english.js | safe | The file contains only a static English wordlist exported as a string array, with no executable code, network activity, or malicious patterns. |
| wordlists/french.js | safe | No malicious patterns detected |
| wordlists/italian.js | safe | No malicious patterns detected |
| wordlists/japanese.js | safe | No malicious patterns detected |
| wordlists/korean.js | safe | No malicious patterns detected; the file only exports a static Korean wordlist string with no code execution or external interaction. |
| wordlists/portuguese.js | safe | No malicious patterns detected |
| wordlists/simplified-chinese.js | safe | No malicious patterns detected; the file only exports a static string containing a list of Chinese words. |
| wordlists/spanish.js | safe | No malicious patterns detected; the file only exports a static wordlist of Spanish words and contains no executable or suspicious code. |
| wordlists/traditional-chinese.js | safe | No malicious patterns detected; the file only exports a static list of traditional Chinese words as a string. |
Affected version ranges
None of the 3 scanned versions of @scure/bip39 are flagged high or critical. The latest scanned version, 1.6.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/bip39
Frequently asked questions
Is @scure/bip39 safe to use?
Our AI source review of @scure/bip39@1.3.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @scure/bip39 contain malware?
No malware was identified in @scure/bip39@1.3.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/bip39 checked?
Togoder Security downloaded the published npm package and had an AI model read its 23 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/bip39 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/bip39@1.3.0, cost nothing.