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
Counts only

Detail took too long to load

496 findings counted. The list did not arrive in time. Reload the page to try again.

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.

Detail took too long to load

18,359 findings counted. The list did not arrive in time. Reload the page to try again.

Stored counts by category

17,863
Network indicators
268
Code patterns
22
Network calls
5
Obfuscation
1
Malware signatures

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