Microsoft Edge Add-ons Verified domain

IronVest

80c40db6-f1db-5193-869e-2da298bb49f4 | Store v9.9.12
83/ 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 18 March 2026
Version
v9.9.12
Detail
Full list

Evidence ledger

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

496 findings
Showing 25 of 227 ยท highest severity first

YARA Rule Matches

16 rules
SeverityRuleHitsFilesMetadata
HIGHmemory shylock 1
mappings.json
https://github.com/jackcr/ FP 10%
HIGHpostinstall crypto operations

Cryptographic operations detected

31
assets/security-manager-a73260da.jspages/post-install/assets/popup-content.svgjs/lib/crypto-js-3.1.9-1/cipher-core.min.js +28 more
Risky Plugins Authors FP 30%
HIGHpostinstall obfuscation

Code obfuscation techniques detected

42
js/lib/mnemonic.jsapi-rules.jsonmanifest.json +39 more
Risky Plugins Authors FP 20%
HIGHcredential env files

Environment configuration file path detected

8
assets/security-manager-a73260da.jscognito-min.jsapi-rules.json +5 more
Risky Plugins Authors FP 10%
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.

1
background.js
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.

4
popup.jsjquery-min.jscommon-content.js +1 more
FP 10%
HIGHpostinstall registry modification

Windows registry modification detected

5
api-rules.jsonbackground.jsmappings.json +2 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.

5
assets/security-manager-a73260da.jspopup.jsbackground.js +2 more
FP 5%
HIGHpostinstall file download

File download activity detected

24
locales/en.jscognito-min.jsassets/security-manager-a73260da.js +21 more
Risky Plugins Authors FP 30%
HIGHcredential steam data

Steam application data path detected

1
mappings.json
Risky Plugins Authors FP 20%
HIGHpostinstall system command

System command execution detected

33
cognito-min.jspanel.jsmappings.json +30 more
Risky Plugins Authors FP 10%
HIGHpostinstall file manipulation

File system manipulation detected

32
pages/vendor.cssjquery-min.jsjs/lib/asmcrypto.min.js +29 more
Risky Plugins Authors FP 20%
HIGHpostinstall network communication

Network communication detected

42
locales/it.jslocales/pt.jslocales/fr.js +39 more
Risky Plugins Authors FP 30%
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.

16
assets/src/entries/biometrics/index-9a3f0dd5.jspopup.jscognito-min.js +13 more
FP 5%
HIGHpostinstall persistence mechanism

Persistence mechanism detected

15
background.jslocales/pt.jscontent.js +12 more
Risky Plugins Authors FP 20%
HIGHpostinstall environment access

Environment variable access detected

9
assets/Refresh-96abff40.jsassets/index-6c8b10f7.jsassets/index-86331efc.js +6 more
Risky Plugins Authors FP 40%

Network Indicators

Concrete URLs, domains, IPs, emails, and hashes extracted from the analyzed artifact.

17,863 total

Loading network indicators

Long lists can take a few seconds.

Publisher Evidence

Limited evidence

IronVest Inc.

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.

38
Publisher domain
ironvest.com
Observed
Store verification signal
Limited signal
Limited
Extension portfolio
4
Portfolio

13 evidence rows available.

Finding Categories

269
Malware Signatures
5
Obfuscation
22
Network
17,863
IoC Indicators

YARA Rules Matched

16 rules(269 hits)
memory shylock postinstall crypto operations postinstall obfuscation credential env files NoUseEval SQLInjection postinstall registry modification LocalStorageShouldNotBeUsed postinstall file download credential steam data postinstall system command postinstall file manipulation postinstall network communication NoUseWeakRandom postinstall persistence mechanism postinstall environment access

AI Security Report

AI Security Review

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

The IronVest extension presents genuinely ambiguous evidence requiring runtime analysis before a definitive verdict can be reached.

The extension is published by "IronVest Inc." with a description stating it protects "Passwords, Payments, and Privacy." This aligns with legitimate password manager functionality. However, the version is listed as "unknown," which creates uncertainty about whether this analysis captured the correct codebase.

The findings show 269 malware-signature detections (severity: high) alongside 5 obfuscation findings. The obfuscation findings specifically identify "OBFUSCATION-large_base64" in common.js and common-content.js. Large base64 strings can be legitimate (embedded assets, images) or malicious (encoded payloads). Without runtime inspection, the purpose of this obfuscation cannot be determined.

Network findings show 22 fetch calls across panel.js:34, panel.js:38, common.js:64, popup.js:32, popup.js:41, popup.js:43, common-content.js:49, common-content.js:96, background.js:44, and content.js:22. Critically, these findings only indicate fetch calls existโ€”they do not reveal the target domains. If these fetch calls transmit data to unknown third-party domains, this would be credential exfiltration. If they call the extension's own backend for legitimate password management features, this is benign.

The 18,144 IoC findings are almost certainly false positive noise from bundled dependencies or IoC extractor garbage patterns (IPv6 fragments, property access chains, CDN domains). The findings summary shows "malware": 0, meaning no actual malware was detectedโ€”only 269 malware-signature matches, which can trigger on code patterns resembling malware families without being malicious.

Counterargument: A skeptic could argue that 269 malware signatures combined with obfuscation in a password manager extension strongly indicates credential theft. This is a reasonable concern. However, the malware-signature count alone does not confirm malicious intent. Many legitimate extensions trigger malware-signature rules on common code patterns. The absence of actual malware detections (malware: 0) and the lack of specific suspicious domains in the network findings prevent a confirmed_malicious verdict. Runtime analysis is required to determine what domains the fetch calls target and whether the base64 content contains malicious payloads or legitimate assets.

Key Reasons

  • 269 malware-signature findings with high severity require investigation
  • Obfuscation (large_base64) in common.js and common-content.js without clear purpose
  • Network fetch calls detected but target domains are not specified in findings
  • Version metadata is unknown, limiting analysis reliability

False Positive Considerations

  • 18,144 IoC findings likely from bundled dependencies and extractor noise
  • Malware-signature findings (not malware detections) can trigger on benign code patterns

Reviewed 2026-04-27; recommended action: runtime analysis; model confidence 55%.

Source Code Viewer

Source Code Not Available

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

Frequently Asked Questions