Microsoft Edge Add-ons Verified domain

Pade - Unified Communications at Work

1f733472-c1e6-562f-a850-cf267fddbc40 | Store v1.6.8
83/ 100
HIGH risk
AI review verdict
Review before use

The AI review rates the findings as likely false positive, but the risk score (83/100) still counts them.

Analysis record

Analysed
8 months ago 17 March 2026
Version
v1.6.8
Detail
Partial list

Evidence ledger

Ranked by severity · findings with a source location link to the code viewer

Showing 1,000 of 3,171 findings.

YARA Rule Matches

22 rules
SeverityRuleHitsFilesMetadata
HIGHOriginsNotVerified

Browsers allow message exchanges between Window objects of different origins. Because any window can send / receive messages from other window it is important to verify the sender's / receiver's identity: When sending message with postMessage method, the identity's receiver should be defined (the wildcard keyword (*) should not be used).\nWhen receiving message with message event, the sender's identity should be verified using the origin and possibly source properties. For more information checkout the OWASP A2:2017 (https://owasp.org/www-project-top-ten/2017/A2_2017-Broken_Authentication) and (https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage) advisory.

6
inverse/plugins/libs/mermaid.min.jsinverse/plugins/libs/rss-library.jscollab/onlyoffice/api.js +3 more
FP 15%
HIGHUntrustedContentShouldNotBeIncluded

Including content in your site from an untrusted source can expose your users to attackers and even compromise your own site. For that reason, this rule raises an issue for each non-relative URL. For more information checkout the OWASP A1:2017 (https://owasp.org/www-project-top-ten/2017/A1_2017-Injection.html) advisory.

4
options/lib/mootools-core.jsinverse/dist/converse.jswebodf/webodf-debug.js +1 more
FP 20%
HIGHpostinstall crypto operations

Cryptographic operations detected

116
tasks/static/css/all.csscollab/onlyoffice/index.jsinverse/plugins/audioconf/stylesheets/font-awesome.css +113 more
Risky Plugins Authors FP 30%
HIGHAlertStatementsShouldNotBeUsed

alert(...) as well as confirm(...) and prompt(...) can be useful for debugging during development, but in production mode this kind of pop-up could expose sensitive information to attackers, and should never be displayed. For more information checkout the CWE-489 (https://cwe.mitre.org/data/definitions/489.html) advisory.

4
akowe/closure/ui/customcolorpalette.jsinverse/plugins/info.jsoptions/settings.js +1 more
FP 10%
HIGHDebuggerStatementsShouldNotBeUsed

The debugger statement can be placed anywhere in procedures to suspend execution. Using the debugger statement is similar to setting a breakpoint in the code. By definition such statement must absolutely be removed from the source code to prevent any unexpected behavior or added vulnerability to attacks in production. For more information checkout the CWE-489 (https://cwe.mitre.org/data/definitions/489.html) advisory.

5
help/assets/plugins/prism/min/prism-min.jsinverse/plugins/audioconf/scripts/jssip.min.jshelp/assets/plugins/prism/prism.js +2 more
FP 10%
HIGHUsingCommandLineArguments

Command line arguments can be dangerous just like any other user input. They should never be used without being first validated and sanitized. Remember also that any user can retrieve the list of processes running on a system, which makes the arguments provided to them visible. Thus passing sensitive information via command line arguments should be considered as insecure. This rule raises an issue when on every program entry points (main methods) when command line arguments are used. The goal is to guide security code reviews. Sanitize all command line arguments before using them. For more information checkout the CWE-88 (https://cwe.mitre.org/data/definitions/88.html) advisory.

3
webodf/webodf-debug.jswodo/wodotexteditor/webodf.jsakowe/editor/webodf-debug.js
FP 20%
HIGHpostinstall obfuscation

Code obfuscation techniques detected

125
inverse/plugins/libs/abcjs_basic.jsakowe/closure/base.jsakowe/closure/dom/pattern/repeat.js +122 more
Risky Plugins Authors FP 20%
HIGHpostinstall file download

File download activity detected

153
inverse/dist/converse.jswebodf/index.htmlcalendar/fullcalendar.min.js +150 more
Risky Plugins Authors FP 30%
HIGHpostinstall registry modification

Windows registry modification detected

70
akowe/closure/debug/reflect.jsakowe/closure/ui/option.jsinverse/plugins/audioconf/scripts/click2dial.js +67 more
Risky Plugins Authors FP 30%
HIGHLocalStorageShouldNotBeUsed

Session storage and local storage are HTML 5 features which allow developers to easily store megabytes of data client-side, as opposed to the 4Kb cookies can accommodate. While useful to speed applications up on the client side, it can be dangerous to store sensitive information this way because the data is not encrypted by default and any script on the page may access it. This rule raises an issue when the localStorage and sessionStorage API's are used. For more information checkout the OWSAP A3:2017 (https://owasp.org/www-project-top-ten/2017/A3_2017-Sensitive_Data_Exposure.html) advisory.

11
options/lib/store.jsakowe/closure/debug/fancywindow.jsoptions/canned/canned.js +8 more
FP 5%
HIGHcredential env files

Environment configuration file path detected

28
inverse/plugins/search.jscollab/index.jsinverse/plugins/info.js +25 more
Risky Plugins Authors FP 10%
HIGHCreatingCookiesWithoutTheSecureFlag

When a cookie is protected with the secure attribute set to true it will not be send by the browser over an unencrypted HTTP request and thus cannot be observed by an unauthorized person during a man-in-the-middle attack. It is recommended to use HTTPs everywhere so setting the secure flag to true should be the default behaviour when creating cookies. For more information checkout the OWASP A3:2017 (https://owasp.org/www-project-top-ten/2017/A3_2017-Sensitive_Data_Exposure.html) advisory.

1
options/lib/mootools-core.js
FP 30%
HIGHNoUseEval

The eval function is extremely dangerous. Because if any user input is not handled correctly and passed to it, it will be possible to execute code remotely in the context of your application (RCE - Remote Code Executuion). For more information checkout the CWE-94 (https://cwe.mitre.org/data/definitions/94.html) advisory.

14
inverse/dist/libsignal-protocol.jsoptions/lib/mootools-core.jsakowe/editor/webodf-debug.js +11 more
FP 10%
HIGHSQLInjection

SQL queries often need to use a hardcoded SQL string with a dynamic parameter coming from a user request. Formatting a string to add those parameters to the request is a bad practice as it can result in an SQL injection. The safe way to add parameters to a SQL query is to use SQL binding mechanisms. For more information checkout the CWE-564 (https://cwe.mitre.org/data/definitions/564.html) and OWASP A1:2017 (https://owasp.org/www-project-top-ten/2017/A1_2017-Injection.html) advisory.

5
inverse/dist/converse.jsinverse/plugins/libs/rss-library.jscalendar/jquery-1.11.3.min.js +2 more
FP 10%
HIGHxtreme rat

Xtreme RAT

1
uport/uport-connect.js
Kevin Falcoz FP 5%
HIGHcredential skype data

Skype data path detected

2
js/background.jsoptions/settings.js
Risky Plugins Authors FP 20%
HIGHpostinstall network communication

Network communication detected

213
akowe/closure/structs/treenode.jsinverse/dist/locales/de-LC_MESSAGES-converse-po.jsakowe/closure/dom/dom_test.js +210 more
Risky Plugins Authors FP 30%
HIGHpostinstall file manipulation

File system manipulation detected

176
help/assets/plugins/prism/prism.cssakowe/closure/object/object.jsinverse/plugins/libs/marked.js +173 more
Risky Plugins Authors FP 20%
HIGHNoUseWeakRandom

When software generates predictable values in a context requiring unpredictability, it may be possible for an attacker to guess the next value that will be generated, and use this guess to impersonate another user or access sensitive information. As the Math.random() function relies on a weak pseudorandom number generator, this function should not be used for security-critical applications or for protecting sensitive data. In such context, a cryptographically strong pseudorandom number generator (CSPRNG) should be used instead. For more information checkout the CWE-338 (https://cwe.mitre.org/data/definitions/338.html) advisory.

54
help/assets/plugins/bootstrap/js/bootstrap.jsakowe/editor/webodf-debug.jsakowe/dependencies/jquery.js +51 more
FP 5%
HIGHReadingTheStandardInput

It is common for attackers to craft inputs enabling them to exploit software vulnerabilities. Thus any data read from the standard input (stdin) can be dangerous and should be validated. Sanitize all data read from the standard input before using it. For more information checkout the CWE-20 (https://cwe.mitre.org/data/definitions/20.html) advisory.

1
inverse/dist/libsignal-protocol.js
FP 10%
HIGHpostinstall persistence mechanism

Persistence mechanism detected

1
wodo/wodotexteditor/widgets/dialogWidgets/fontEffectsPane.js
Risky Plugins Authors FP 20%
HIGHpostinstall system command

System command execution detected

3
akowe/dependencies/moment.jschangelog.htmlinverse/plugins/libs/jspdf.debug.js
Risky Plugins Authors FP 10%

Publisher Evidence

Low

Inspired Futures Ltd

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.

45
Publisher domain
github.com
Trusted match
Store verification signal
Limited signal
Limited
Extension portfolio
1
Portfolio

13 evidence rows available.

Finding Categories

996
Malware Signatures
4
Obfuscation

YARA Rules Matched

22 rules(996 hits)
OriginsNotVerified UntrustedContentShouldNotBeIncluded postinstall crypto operations AlertStatementsShouldNotBeUsed DebuggerStatementsShouldNotBeUsed UsingCommandLineArguments postinstall obfuscation postinstall file download postinstall registry modification LocalStorageShouldNotBeUsed credential env files CreatingCookiesWithoutTheSecureFlag NoUseEval SQLInjection xtreme rat credential skype data +6 more

AI Security Report

AI Security Review

Evidence context: threat category none; evidence quality moderate.

Pade is a unified communications extension published by Inspired Futures Ltd. The network findings reveal legitimate communication library usage: inverse/dist/converse.js contains XMPP library calls (findings NET-XMLHTTPREQUEST at line 54438, NET-FETCH at line 71285, NET-WEBSOCKET at line 50691), inverse/dist/libsignal-protocol.js contains Signal encryption protocol code (NET-FETCH at line 34987, NET-XMLHTTPREQUEST at line 3863), and akowe/dependencies/lib-jitsi-meet.min.js contains video conferencing library code (NET-WEBSOCKET at line 1573). These are all legitimate libraries for unified communications functionality.

The 1475 malware signatures are almost certainly false positives from bundled dependencies in the inverse/dist/ directory. This is a known CVEQ false positive pattern: minified/bundled JavaScript from npm packages triggers YARA rules designed to catch malware patterns. The absence of any actual IoC findings (0 in the evidence) confirms no suspicious domains are present. The 9 obfuscation findings are likely from minification rather than malicious obfuscation, and critically, there are 0 code-smell findings, which would typically accompany genuine malware.

The network calls are all in expected locations: js/background.js (line 2033), options/settings.js (line 1205), and inverse/plugins/webmeet.js (line 1905) - these are standard extension architecture files for a communications app.

Counterargument: A skeptic might argue that 1475 malware signatures is too high to dismiss, and the "unknown" version combined with 0 users suggests a suspicious new extension. However, the nature of the findings contradicts this: all network activity is in legitimate communication libraries, there are zero suspicious IoCs, and the malware signatures are in bundled dist/ files where false positives are expected. The "unknown" version is a data quality issue from the store metadata, not evidence of malicious behavior. If this were actual malware, we would expect suspicious domains in IoCs or code-smell findings, neither of which exist.

Key Reasons

  • All network findings in legitimate communication libraries (converse.js, libsignal-protocol.js, lib-jitsi-meet.min.js)
  • Zero IoC findings - no suspicious domains detected
  • Zero code-smell findings - genuine malware typically triggers these
  • Malware signatures in bundled dist/ directory - known false positive pattern
  • Extension functionality matches stated purpose (unified communications)

False Positive Considerations

  • Bundled dependencies in dist/ directory triggering YARA rules
  • Minified JavaScript from legitimate libraries matching malware patterns
  • No suspicious IoC domains found
  • Zero code-smell findings despite high signature count

Reviewed 2026-04-27; recommended action: suppress false positive; model confidence 72%.

Source Code Viewer

Source Code Not Available

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

Frequently Asked Questions