Summary
Togoder Security scanned the npm package @metamask/scure-bip39@2.1.1 on Oct 4, 2026. An AI review of 10 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 |
|---|---|---|
| dist/index.js | safe | No malicious patterns detected; the code is a legitimate BIP39 mnemonic implementation using standard cryptographic libraries without exfiltration, obfuscation, or suspicious behavior. |
| dist/wordlists/czech.js | safe | No malicious patterns detected |
| dist/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. |
| dist/wordlists/french.js | safe | No malicious patterns detected |
| dist/wordlists/italian.js | safe | No malicious patterns detected |
| dist/wordlists/japanese.js | safe | No malicious patterns detected |
| dist/wordlists/korean.js | safe | No malicious patterns detected; the file only exports a static Korean wordlist string with no code execution or external interaction. |
| dist/wordlists/simplified-chinese.js | safe | No malicious patterns detected; the file only exports a static string containing a list of Chinese words. |
| dist/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. |
| dist/wordlists/traditional-chinese.js | safe | No malicious patterns detected; the file only exports a static list of traditional Chinese words as a string. |
Frequently asked questions
Is @metamask/scure-bip39 safe to use?
Our AI source review of @metamask/scure-bip39@2.1.1 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @metamask/scure-bip39 contain malware?
No malware was identified in @metamask/scure-bip39@2.1.1 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 @metamask/scure-bip39 checked?
Togoder Security downloaded the published npm package and had an AI model read its 10 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 @metamask/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 @metamask/scure-bip39@2.1.1, cost nothing.