Dictionariez - Dictionary Lookup & AI Translation for Language Learning
Based on the RiskyPlugins AI security review of the observed evidence. The review covers version 8.1.2, not the analysed version 9.4.0.
Analysis record
- Analysed
- Today 21 November 2026
- Version
- v9.4.0
- Artifact
- SHA256 010cc222…e93ccc
- Detail
- Full list
Evidence ledger
Ranked by severity · findings with a source location link to the code viewer
Publisher Evidence
Limited evidenceRiver Young
Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.
Edge does not expose the same publisher verification data as IDE stores, so this score is deliberately conservative.
13 evidence rows available.
Finding Categories
AI Security Report
AI Security Review
Evidence context: threat category none; evidence quality moderate.
The extension describes itself as a customizable dictionary tool supporting double-click lookups in over 20 languages, 1000 dictionaries, and Anki integration. A review of its manifest data reveals a complete absence of declared permissions and host_permissions. It also has no extracted network endpoints or indicators of compromise. This means the extension does not request the broad access typically required to read all web page content or track browsing history.
The security scan identified three medium-severity network findings titled NET-FETCH-206.bundle.js-1, NET-FETCH-preinject.bundle.js-1, and NET-FETCH-speak.bundle.js-1. These detections simply mean the scanner found standard network request functions like fetch or XMLHttpRequest within those specific files. The file names themselves point to normal application architecture. 206.bundle.js is a standard webpack chunk identifier, preinject.bundle.js handles content script preparation, and speak.bundle.js clearly manages text-to-speech audio. For an extension that promises AI translation and dictionary lookups, making outbound network requests to fetch definitions and audio files is its primary function. The scanner does not flag the destination of these requests, only the presence of the network call mechanism itself.
There are zero malware signatures, zero obfuscation findings, and zero code-smell alerts in the scan results. The remaining 36 informational findings are routine static analysis artifacts that do not indicate malicious behavior. No suspicious domains or tracking endpoints were extracted from the codebase. This clean profile stands in stark contrast to actual malicious extensions, which typically hide their network traffic behind obfuscated code or route it through unknown proxy servers.
A skeptic might point out that the developer name is empty and the user count is zero, which are common traits of abandoned or malicious extensions. However, the extension is on version 8.1.2, indicating a long development history rather than a freshly minted throwaway package. The missing metadata is far more likely a quirk of the Edge store data extraction or a delisted status than evidence of malice. Without any actual malicious payloads, suspicious domains, or invasive permissions, the network flags are just the sound of a dictionary tool doing its job.
Key Reasons
- No malicious signatures, obfuscation, or suspicious IoCs were detected.
- Network findings are limited to standard fetch API calls in functional modules like speak.bundle.js.
- The extension declares no host permissions or broad browser permissions.
- File names indicate standard webpack bundling for translation and text-to-speech features.
False Positive Considerations
- NET-FETCH detections on standard webpack bundles representing normal API calls
- Functional module names like speak.bundle.js indicating legitimate text-to-speech features
Reviewed 2026-10-10 · version 8.1.2; recommended action: suppress false positive; model confidence 85%.
Edge version history
Risk trend by version
14 analyzed versions. Each point is the latest successful scan for that version; failed zero-score scans are hidden. Dates: First seen by Risky Plugins.
Pick any point on the chart, then open the Source tab to read that version's code.
Source Code Not Available
Source code is not available for this version of the extension.
Frequently Asked Questions
Similar Extensions
Related extensions from the same publisher or marketplace