AI Auto Form Filler (BYOK)
From the RiskyPlugins AI security review of the observed evidence.
Analysis record
- Analysed
- 4 days ago
- Version
- v2.3.2
- Artifact
- SHA256 2B8…40C
- Source
- Findings (non-IoC)
Is AI Auto Form Filler (BYOK) safe?
AI Auto Form Filler (BYOK) declares no special permissions and no host permissions. Its listed network names include dracon.uk, nodefilter.show, ut.info, and ko-fi.com. The code has fetch findings in background.js:6:0 and chunks/testConnection-CKt0YMlk.js:1:0, plus a socket finding in content-scripts/content.js:212:0. These details describe connections the extension can make through its own code, without a manifest permission string granting broad site or cookie access.
The main warning is OBFUSCATION-UNICODE_HEAVY-chunks/options-C8ugsTKv.js-1 in chunks/options-C8ugsTKv.js:1:0. If that match comes from hidden code or encoded settings, it would make the extension's behavior harder to inspect. The listed results contain no malware-signature match, so the Unicode finding needs context from the source file and the network requests.
The extension has a small declared access surface, and dracon.uk matches the developer name Dracon. The scanner still found unfamiliar destinations at nodefilter.show and ut.info, along with socket activity in content-scripts/content.js:212:0. Those findings leave the extension's network behavior unresolved; a runtime check would show which requests run during form filling and what data they carry.
Evidence ledger
Ranked by severity · findings with a source location link to the code viewer
YARA Rule Matches
12 rules| Severity | Rule | Hits | Files | Metadata |
|---|---|---|---|---|
| LOW | postinstall file download | 6 | content-scripts/content.jsbackground.jschunks/testConnection-CKt0YMlk.js +3 more | - |
| LOW | SQLInjection | 1 | content-scripts/content.js | - |
| LOW | NoUseWeakRandom | 3 | content-scripts/content.jsbackground.jschunks/popup-DsQikn2O.js | - |
| LOW | postinstall crypto operations | 3 | chunks/options-C8ugsTKv.jscontent-scripts/content.jsbackground.js | - |
| LOW | postinstall system command | 19 | content-scripts/content.jsassets/shared-tokens.cssassets/practice-form-B6vPOuNf.css +16 more | - |
| LOW | postinstall file manipulation | 12 | chunks/welcome-oT9IV_PH.jsoptions.htmlassets/options-erNFJZ8M.css +9 more | - |
| LOW | postinstall environment access | 3 | chunks/popup-DsQikn2O.jschunks/style-D6McMGC4.jschunks/options-C8ugsTKv.js | - |
| LOW | postinstall obfuscation | 3 | content-scripts/content.jsbackground.jschunks/practiceForm-CpD0THMb.js | - |
| LOW | postinstall network communication | 14 | chunks/welcome-oT9IV_PH.jschunks/style-D6McMGC4.jsoptions.html +11 more | - |
| LOW | credential metamask extension | 1 | chunks/popup-DsQikn2O.js | - |
| LOW | credential env files | 1 | content-scripts/content.js | - |
| LOW | postinstall persistence mechanism | 2 | content-scripts/content.jsbackground.js | - |
Network Indicators
Concrete URLs, domains, IPs, emails, and hashes extracted from the analyzed artifact.
Network indicators are queued for lazy loading
Scroll this section into view to load the detailed rows.
Publisher Evidence
Limited evidenceDracon
Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.
Firefox does not expose the same publisher verification data as IDE stores, so this score is deliberately conservative.
12 evidence rows available.
Finding Categories
YARA Rules Matched
12 rules(68 hits)Requested Permissions
3 permissionsAI Security Report
AI Security Review
Evidence context: threat category unknown malware; evidence quality moderate.
AI Auto Form Filler (BYOK) is presented as a form-filling tool, and the name identifies a bring-your-own-key design. The manifest data lists no permissions and no host permissions, which limits the browser access visible in this review. The code still contains network activity: NET-FETCH-background.js-6 points to background.js:6:0, NET-FETCH-chunks/_virtual_wxt-html-plugins-DPbbfBKe.js-1 points to chunks/_virtual_wxt-html-plugins-DPbbfBKe.js:1:0, and NET-FETCH-chunks/testConnection-CKt0YMlk.js-1 points to chunks/testConnection-CKt0YMlk.js:1:0. NET-SOCKET_IO-content-scripts/content.js-212 also identifies socket activity at content-scripts/content.js:212:0.
The network names need attention because nodefilter.show, ut.info, and dracon.uk are listed alongside familiar development or service names such as svelte.dev, wxt.dev, mozilla.com, ko-fi.com, and www.roboform.com. The endpoint list alone does not show what data is sent, whether these hosts belong to the developer, or whether they are loaded during normal form filling. dracon.uk matches the developer name Dracon, while the supplied data gives no ownership detail for nodefilter.show or ut.info. Runtime capture of requests from background.js:6:0, chunks/testConnection-CKt0YMlk.js:1:0, and content-scripts/content.js:212:0 would resolve that gap.
The clearest code concern is OBFUSCATION-UNICODE_HEAVY-chunks/options-C8ugsTKv.js-1 at chunks/options-C8ugsTKv.js:1:0. A Unicode-heavy pattern can come from compressed or generated application code, yet this finding does not identify the characters, their purpose, or any linked behavior. The file is named options, so a check of its readable source and decoded strings should establish whether the pattern belongs to interface text, configuration handling, or concealed logic. The listed scan results contain no malware-signature or tool-poisoning finding, and the concrete alerts are limited to the network and Unicode findings named above.
A skeptic could point to the empty permission lists and the BYOK name as signs of a small, privacy-focused utility. That case is supported by the absence of browser permissions and by the developer-linked endpoint dracon.uk. It does not resolve the separate nodefilter.show and ut.info destinations, the socket alert in content-scripts/content.js:212:0, or the Unicode-heavy match in chunks/options-C8ugsTKv.js:1:0. Those items leave intent and data handling unclear, so a clean verdict would go beyond the supplied evidence. Runtime network inspection and source review are the direct ways to settle the ambiguity.
Key Reasons
OBFUSCATION-UNICODE_HEAVY-chunks/options-C8ugsTKv.js-1flags Unicode-heavy content inchunks/options-C8ugsTKv.js:1:0.NET-SOCKET_IO-content-scripts/content.js-212identifies socket activity atcontent-scripts/content.js:212:0.- Fetch findings in
background.js:6:0andchunks/testConnection-CKt0YMlk.js:1:0need request-level review. nodefilter.showandut.infoare listed network destinations without ownership or purpose details.- No permissions or host permissions are declared, and no malware-signature finding is listed.
False Positive Considerations
- The Unicode-heavy match in
chunks/options-C8ugsTKv.js:1:0may result from generated or compressed application code. - The fetch findings in
background.js:6:0andchunks/testConnection-CKt0YMlk.js:1:0can fit a connection-test or service-backed form filler. - The network list includes development and service domains such as
svelte.dev,wxt.dev, andmozilla.com. - The extension declares no permissions or host permissions, limiting the access shown in the manifest.
Reviewed 2026-09-29; recommended action: runtime analysis; model confidence 76%.
Firefox version history
Risk trend by version
4 analyzed versions. Each point is the latest successful scan for that version; failed zero-score scans are hidden. Dates are based on first seen by risky plugins.
Pick any point on the chart to explore that version's code below.
Source Code Not Available
Source code is not available for this version of the extension.
About This Extension
Frequently Asked Questions
Similar Extensions
Related extensions from the same publisher or marketplace