Brown Noise Generator
Based on the RiskyPlugins AI security review of the observed evidence. The review covers version 1.2.1, not the analysed version 1.2.3.
Analysis record
- Analysed
- Today 22 November 2026
- Version
- v1.2.3
- Artifact
- SHA256 70056079…9d56b4
- Detail
- Full list
Is Brown Noise Generator safe?
Brown Noise Generator plays brown, pink and white noise and includes a focus timer, with no ads and no sign-up. It declares no permissions and no host permissions. That means it cannot read the pages you visit, cannot touch your cookies, tabs or downloads, and has no way to change your search engine. The only network addresses recorded in its code are google-analytics.com and www.google-analytics.com, along with hearth.energy and panarini.github.io.
The one network finding, NET-FETCH-track.js-48, is a fetch call inside track.js. If that call were shipping your browsing activity to an unknown server, it would be a real problem. Its destination is a Google Analytics collector, which is how a developer counts installs and usage. Nothing in the code points at a login page, a banking site or a place to send stolen data.
The scanner's loudest alarm comes from _locales/fa/messages.json, the Farsi translation file. It flagged invisible zero-width characters there as hidden content, but those characters are part of how Persian is written and appear in every Farsi locale file. The rest of the noise is 39 code-smell rules that fire on ordinary JavaScript, plus 15 indicator matches that are fragments of minified code. Entries like st.la and st.pa are not real addresses.
If you want a reason to skip it, track.js is the one. An extension with no privacy policy that reports usage to Google is a fair thing to avoid on principle. For what it actually does, it holds the permissions of a calculator and a translation file that trips a scanner.
Evidence ledger
Ranked by severity · findings with a source location link to the code viewer
Publisher Evidence
Limited evidencedev--2d80c111-b010-2c14-7257-8d56736a332b
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.
12 evidence rows available.
Finding Categories
Requested Permissions
4 permissionsAI Security Report
AI Security Review
Evidence context: threat category none; evidence quality moderate.
Brown Noise Generator (version 1.2.1, Chrome Web Store, about 141 users) is a single-purpose audio extension: brown, pink and white noise plus a focus timer, published by an individual developer reachable at [email removed]. Its manifest declares no permissions and no host_permissions. That matters more than any finding count here. Without host permissions the extension cannot read or change the pages you visit, and without API permissions it cannot reach cookies, tabs, history, downloads or the clipboard.
Of the 56 recorded findings, 39 are code-smell rules and 15 are indicator matches, categories that fire on ordinary bundled JavaScript and on minified string fragments. The indicator list is the usual noise: google-analytics.com and www.google-analytics.com are Google's analytics hosts, and entries such as st.la, st.pa, st.ph and st.tw are four-character fragments the extractor carved out of minified code rather than routable addresses. The one network finding worth naming is NET-FETCH-track.js-48, a fetch call at line 48 of track.js. The call points at a Google Analytics collector. That is usage counting, and no code path in the evidence carries page contents, form data or credentials off the machine. The endpoint list also includes hearth.energy and panarini.github.io. Neither is a known malware host, and hearth.energy is the one address worth checking if you want to know who receives anything.
The single high-severity item is an obfuscation match, OBFUSCATION-INVISIBLE_ZERO_WIDTH-_locales/fa/messages.json-0. That file is the Farsi translation table. Zero-width joiners and non-joiners are required characters in Persian text and show up in every Farsi locale file; they are not steganography. A scanner that hunts for invisible Unicode will always flag _locales/fa/messages.json, along with the Sinhala, Kannada and Khmer locale files in other extensions, and the same rule fired here.
No malware signature matched. Nothing in the dependency, secret, manifest-analysis or tool-poisoning categories fired either. Nothing in the evidence resembles credential theft, browser hijacking, proxyware or a bundled miner.
A skeptic would point at track.js and argue that an extension which phones home should be treated as a tracking tool, especially one from a Gmail address with no company behind it. That is a fair reading of the file name, and analytics without a privacy policy is a reason to skip an extension if you care about that. The threat classes are still different. Tracking code that reports to google-analytics.com does not steal sessions or rewrite searches, and the manifest gives this extension no channel through which to send anything worth taking. The rest of the noise comes from rules that fire on trivial JavaScript and from a locale file that could not be removed without breaking Persian support.
What would change this verdict: a network endpoint that is not Google, a permission such as cookies or <all_urls>, or a fetch in track.js that carries page content. None of those are present.
Key Reasons
- Manifest declares no permissions and no host permissions, so the extension cannot read or alter page content, cookies, tabs or history.
- No malware, malware-signature, secret, dependency, manifest-analysis or tool-poisoning findings fired; the 39 code-smell and 15 IoC entries are known noise sources.
- The only network finding, NET-FETCH-track.js-48, resolves to google-analytics.com, ordinary usage telemetry rather than exfiltration.
- The sole high-severity finding, OBFUSCATION-INVISIBLE_ZERO_WIDTH-_locales/fa/messages.json-0, matches required zero-width characters in Persian text.
- IoCs such as st.la, st.pa, st.ph and st.tw are four-character fragments of minified JavaScript, not routable domains.
False Positive Considerations
- OBFUSCATION-INVISIBLE_ZERO_WIDTH fired on _locales/fa/messages.json, a Farsi locale file where zero-width joiners are legitimate writing-system characters.
- 15 IoC entries are minified-JS fragments (st.la, st.pa, st.ph, st.tw) and Google analytics hosts, not suspicious destinations.
- 39 low-severity code-smell rules dominating the finding count, consistent with the documented score-inflation bias.
- No permissions or host permissions declared, so capability-based findings cannot be supported by the manifest.
Reviewed 2026-10-12 · version 1.2.1; recommended action: suppress false positive; model confidence 85%.
Chrome 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: 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.
About This Extension
Frequently Asked Questions
Similar Extensions
Related extensions from the same publisher or marketplace