Chrome Web Store Verified domain

Keeper Wallet

by dev--32aba3c7-c109-4737-004a-984c73d6d3ee · 10.0K users · 4.7 rating
51bcdc4f-0af6-586b-929c-a8c23c8c03a9 | Store v2.13.10
87/ 100
CRITICAL risk
AI review verdict
Do not install

The AI review rates the findings as likely false positive. The risk score (87/100) comes from stored counts that the review could not adjust. A new analysis will update it.

Analysis record

Analysed
11 months ago 30 November 2025
Version
v2.13.10
Artifact
SHA256 9faf2fa5…d51e80
Detail
Counts only, rows expired

Detail for this analysis has expired

This analysis ran on 30 November 2025. 237 findings counted, and the counts are kept. The individual rows have aged out of storage. A new analysis restores them.

Detail for this analysis has expired

This analysis ran on 30 November 2025. 2,047 network indicators counted, and the counts are kept. The individual rows have aged out of storage. A new analysis restores them.

Publisher Evidence

Limited evidence

dev--32aba3c7-c109-4737-004a-984c73d6d3ee

Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.

Chrome does not expose the same publisher verification data as IDE stores, so this score is deliberately conservative.

47
Publisher domain
waves.tech
Observed
Store verification signal
Limited signal
Limited
Extension portfolio
2
Portfolio

11 evidence rows available.

Detail for this analysis has expired

This analysis ran on 30 November 2025. 2,284 findings counted, and the counts are kept. The individual rows have aged out of storage. A new analysis restores them.

Stored counts by category

2,047
Network indicators
234
Malware signatures
230
Code patterns
1
Manifest
1
Network calls
1
Obfuscation

AI Security Report

AI Security Review

Evidence context: threat category none; evidence quality strong.

This extension presents a classic false-positive scenario driven by known CVEQ detection noise. The 236 total findings are overwhelmingly composed of code-smell detections (230 findings) that match benign JavaScript patterns. The four findings labeled as malware-signatures are all from postinstall_* YARA rules—specifically YARA--postinstall_crypto_operations, YARA--postinstall_file_manipulation, YARA--postinstall_network_communication, and YARA--postinstall_system_command. These rules are well-documented false positives that trigger on basic Node.js operations like fetch, exec, fs, and crypto, which are standard in legitimate applications. Notably, all four of these findings reference unknown_file as the file path, indicating they cannot be attributed to specific source code and likely originate from bundled dependencies.

The single network finding detected a fetch call in accounts.js, which is expected behavior for a blockchain wallet extension that must communicate with Waves network services. The manifest analysis flagged the tabs permission, which is standard for wallet extensions that need to interact with decentralized applications across browser tabs. There are zero actual malware family detections (such as known malware signatures), zero obfuscation findings, and zero suspicious IoCs (domains or IPs). The extension is published by [email removed], an identifiable developer account associated with the Waves blockchain project, not an anonymous publisher.

The strongest counterargument would be that 234 findings marked as high-severity should warrant concern. However, finding count is not evidence of malicious behavior—finding nature is. The severity labels on postinstall rules are misleading; these are code-smell patterns that fire on almost any non-trivial JavaScript codebase. A legitimate blockchain wallet performing cryptographic operations and file handling will naturally trigger these rules. The actual security-relevant categories—malware signatures, obfuscation, and suspicious IoCs—all show zero findings. This extension's behavior aligns with its stated purpose as a Waves blockchain wallet, and the detection noise reflects known limitations in the automated scanning system rather than actual malicious activity.

Key Reasons

  • All malware-signature findings are postinstall_* YARA rules known to produce false positives on benign Node.js code
  • Zero actual malware family signatures, zero obfuscation findings, zero suspicious IoCs detected
  • 230 of 236 findings are code-smell patterns that match legitimate JavaScript
  • Publisher is identifiable ([email removed]) rather than anonymous
  • Single network finding in accounts.js is expected for blockchain wallet functionality

False Positive Considerations

  • postinstall_* YARA rules matching benign Node.js patterns
  • Code-smell findings from bundled dependencies
  • High severity labels on known false-positive rules
  • Unknown file paths indicating bundled/compiled code attribution issues

Reviewed 2026-05-23 · version 2.13.10; recommended action: suppress false positive; model confidence 87%.

Source Code Viewer

Source Code Not Available

Source code is not available for this version of the extension.

About This Extension

🔷 Store your account keys securely Seed phrases and private keys are encrypted and stored within the extension and cannot be accessed by the dApps and services on the web, giving you peace of mind that your funds are always safe from hackers and malicious sites. 🔷 Manage your assets – Check full asset info and balance, add assets to favourites and filter them by name or ID – Transfer assets and NFTs quickly and intuitively: hover over the three dots next to the asset or NFT and choose the transfer arrow option. – Exchange assets instantly directly in Keeper. Click the “Swap” button, select the pair of assets and specify the amount. 🔷 Sign transactions Third-party applications are required to request your signature for each transaction. Before signing, you can review the transaction details, then confirm or reject it. Complete transactions with just one click, no need to enter any sensitive information. 🔷 Switch between wallets You can create or import multiple Waves wallets and switch between them easily. 🔷 Backup your accounts Export your accounts to the encrypted Keystore file and store it in a safe place. Use it to restore access to your accounts or import them into Keeper on a new device. To create the backup, go to settings and select “Export accounts”. 🔷 View transaction history Keeper displays up to 100 most recent transactions for each account. You can apply a range of filtering options, including transactions with incoming or outgoing transfers, transaction ID, asset ID or name, and wallet address.

Frequently Asked Questions