Yours Wallet

AI Security Review

Evidence context: threat category none; evidence quality moderate.

Yours Wallet is a non-custodial wallet for BSV and 1Sat Ordinals, published by [email protected] and installed by about 2,000 Chrome users. A wallet like this has to reach chain indexers and sync servers to display balances and broadcast transactions, so network calls from background.js are part of the job. The useful question is where those calls go.

The endpoint list shows how little of the alert volume is real. Most of the 1,103 IoC entries are not domains: action.app, action.no, aliases.prime, animation.play, bn.bn and bs.nextrequestmsecs-date.now are property access chains and a date expression lifted from minified JavaScript. The entries that read as actual hosts belong to the BSV services this wallet depends on, including bitcoinschema.org, bsvblockchain.tech, apicontext.services and accountcontext.synccontext.services. The last two sit on the .services top-level domain and look like the wallet's own API and account sync hosts. None of them resemble a search hijack domain, an ad exchange, or a page built to collect logins.

The obfuscation hits track the build output. OBFUSCATION-LARGE_BASE64 fires in assets/crypto-CJQadA7Q.js, assets/index-BGtnOb43.js and assets/sweep-tab-DfZyeOVm.js, which are Vite chunks where encoded key material, mnemonics and library payloads live. The same flag in inject.js and content.js matches the provider script a wallet injects into pages so that apps can request a signature. OBFUSCATION-FUNCTION_INDIRECT in background.js and assets/crypto-CJQadA7Q.js is what bundler function wrapping looks like after minification. The NET-FETCH and NET-SOCKET_IO entries in background.js, such as NET-SOCKET_IO-background.js-79742, describe a service worker holding a socket open to a sync backend so the wallet learns about new blocks and ordinals. The 219 code-smell results tag ordinary JavaScript patterns across bundled libraries and carry no weight here.

The strongest case against this reading is YARA--supply_chain_sourcemap_appended_iife in assets/crypto-CJQadA7Q.js.map. Appending an IIFE after the JSON in a sourcemap is a real technique in npm supply-chain compromises, because injected code hides in a file reviewers skim past. In this build the match sits in a .map file, which browsers load only when developer tools are open and which the extension never executes. A payload that cannot run is an odd thing to hide inside a wallet that holds private keys. Comparing assets/crypto-CJQadA7Q.js.map against the upstream Yours Wallet repository would confirm whether the appended block comes from the build pipeline.

One gap affects confidence. The manifest scan recorded no permissions and no host permissions, which a wallet of this type cannot operate without. That reads as a parsing miss rather than a stripped manifest, and it leaves what the extension can reach less clear than the source itself.

Key Reasons

• Published by a named developer ([email protected]) as an open-source non-custodial BSV wallet, with no attempt to mimic a popular extension's name, icon or brand.
• The 1,103 IoC entries are dominated by property-access chains and expressions misread as domains, including action.app, aliases.prime and bs.nextrequestmsecs-date.now.
• Real endpoints resolve to BSV infrastructure the wallet needs: bitcoinschema.org, bsvblockchain.tech, apicontext.services and accountcontext.synccontext.services.
• Obfuscation flags sit on Vite build artifacts in assets/ plus inject.js and content.js, matching base64 key material and a page-injected provider script rather than a hidden payload.
• The single high-severity YARA hit is on assets/crypto-CJQadA7Q.js.map, a sourcemap that is never executed at runtime.

False Positive Considerations

• IoC extractor parsed minified JavaScript property chains as network domains (action.app, bn.bn, aliases.prime, animation.play)
• Vite/Rollup minified chunks trigger LARGE_BASE64 and FUNCTION_INDIRECT obfuscation rules on crypto and library code
• 219 code-smell hits generated by bundled third-party libraries
• Supply-chain sourcemap rule fired on a .map file that no runtime path loads

Reviewed 2026-10-12; recommended action: monitor; model confidence 75%.