Microsoft Edge Add-ons Verified domain

XML Formatter

ac725ecb-e9a2-50dc-a894-c6f9217d2e84 | Store v1.0.5
79/ 100
HIGH risk
AI review verdict
Needs follow up

From the RiskyPlugins AI security review of the observed evidence.

Analysis record

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

Evidence ledger

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

Showing 1,000 of 1,461 findings.
Showing 25 of 934 ยท highest severity first

YARA Rule Matches

13 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.

1
libs/ace.js
FP 15%
HIGHPonmocup

Ponmocup plugin detection (memory)

1
css/icons/512x512.png
Danny Heppener, Fox-IT FP 5%
HIGHpostinstall crypto operations

Cryptographic operations detected

9
libs/jquery-3.5.1.min.jslibs/bootstrap-5.0.1/js/bootstrap.bundle.min.js.maplibs/bootstrap-icons-1.5.0/index.html +6 more
Risky Plugins Authors FP 30%
HIGHpostinstall system command

System command execution detected

8
libs/ace.jslibs/worker-xml.jslibs/jquery-3.5.1.min.js +5 more
Risky Plugins Authors FP 10%
HIGHpostinstall network communication

Network communication detected

10
libs/bootstrap-icons-1.5.0/bootstrap-icons.jsonlibs/bootstrap-icons-1.5.0/bootstrap-icons.svglibs/bootstrap-icons-1.5.0/gear-wide-connected.svg +7 more
Risky Plugins Authors FP 30%
HIGHpostinstall file manipulation

File system manipulation detected

9
app.jslibs/jquery-3.5.1.min.jsbackground.js +6 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.

3
libs/bootstrap-5.0.1/js/bootstrap.bundle.min.jslibs/jquery-3.5.1.min.jslibs/bootstrap-5.0.1/js/bootstrap.bundle.min.js.map
FP 5%
HIGHpostinstall registry modification

Windows registry modification detected

3
libs/ace.jslibs/bootstrap-5.0.1/js/bootstrap.bundle.min.js.maplibs/worker-xml.js
Risky Plugins Authors FP 30%
HIGHpostinstall file download

File download activity detected

10
libs/bootstrap-icons-1.5.0/index.htmllibs/bootstrap-icons-1.5.0/bootstrap-icons.jsonlibs/bootstrap-icons-1.5.0/cloud-download-fill.svg +7 more
Risky Plugins Authors FP 30%
HIGHcredential env files

Environment configuration file path detected

2
libs/ace.jslibs/bootstrap-5.0.1/js/bootstrap.bundle.min.js.map
Risky Plugins Authors 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.

2
libs/worker-xml.jslibs/jquery-3.5.1.min.js
FP 10%
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.

1
app.js
FP 5%
HIGHpostinstall obfuscation

Code obfuscation techniques detected

7
libs/bootstrap-5.0.1/js/bootstrap.bundle.min.jslibs/ace.jslibs/worker-xml.js +4 more
Risky Plugins Authors FP 20%

Publisher Evidence

Limited evidence

LinangData

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.

52
Publisher domain
linangdata.com
Observed
Store verification signal
Limited signal
Limited
Extension portfolio
38
Portfolio

12 evidence rows available.

Finding Categories

66
Malware Signatures
2
Obfuscation
4
Network

YARA Rules Matched

13 rules(66 hits)
OriginsNotVerified Ponmocup postinstall crypto operations postinstall system command postinstall network communication postinstall file manipulation NoUseWeakRandom postinstall registry modification postinstall file download credential env files SQLInjection LocalStorageShouldNotBeUsed postinstall obfuscation

AI Security Report

AI Security Review

Evidence context: threat category unknown malware; evidence quality moderate.

The XML Formatter extension by LinangData presents an ambiguous security profile requiring further investigation. The analysis reveals 1,461 total findings, but the nature of these findings matters more than the count.

Malware Signatures (66 findings): The extension triggered 66 malware signature matches, which is the primary concern. However, the evidence bundle does not specify which YARA rules fired or what code triggered them. Given the presence of bundled third-party librariesโ€”specifically libs/ace.js (a code editor library) and libs/bootstrap-icons-1.5.0/ (UI assets)โ€”these signatures could be false positives from legitimate bundled code. The ace.js library alone is a large, complex codebase that frequently triggers generic malware signatures.

Network Behavior (4 findings): Network findings are benign and consistent with legitimate XML formatting functionality. app.js:20, app.js:29, and app.js:40 show jQuery AJAX calls, which are expected for an extension that may fetch or process XML content. The libs/ace.js:3969 finding shows XMLHttpRequest usage within the bundled Ace editor library, also expected behavior.

Critical Data Gaps: The version is listed as 'unknown', which prevents proper version-specific threat assessment. Additionally, the user count is 0, which is unusual for a legitimate extension and may indicate the extension was removed from the store, is brand new, or has been flagged for removal.

Positive Signals: Notably, there are zero IoC findingsโ€”no suspicious domains, IPs, or external endpoints were detected. This is significant because malicious extensions typically communicate with command-and-control servers or data exfiltration endpoints. The absence of IoCs suggests the extension does not perform suspicious network communication.

Strongest Counterargument: A skeptic would argue that 66 malware signatures cannot be dismissed as false positives without seeing the specific rules that fired. This is validโ€”66 signatures is a substantial number that warrants investigation. However, without IoC findings, suspicious network behavior, or evidence of credential theft, the signatures alone do not confirm malicious intent. The signatures could stem from bundled libraries, minified code, or overly broad YARA rules that match legitimate patterns.

Recommendation: Reanalysis with version metadata and detailed malware signature breakdown is required to determine if these 66 signatures represent actual malware or false positives from bundled code.

Key Reasons

  • 66 malware signatures require verification to distinguish from bundled library false positives
  • Version metadata is unknown, limiting threat assessment accuracy
  • Zero user count is unusual and may indicate store removal or new listing
  • No suspicious IoCs found despite high total finding count
  • Network behavior is consistent with legitimate XML formatting functionality

False Positive Considerations

  • Bundled libraries (ace.js, bootstrap-icons) likely trigger signature matches
  • Minified/bundled JavaScript may trigger obfuscation rules
  • Version metadata missing prevents proper context assessment
  • Generic YARA rules may match legitimate code patterns in large libraries

Reviewed 2026-04-28; recommended action: reanalyze; model confidence 65%.

Source Code Viewer

Source Code Not Available

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

Frequently Asked Questions