We recently had our extension, Ambire Web3 Wallet, delisted due to what your rejection email vaguely described as “deceptive, misleading, or fraudulent activity or functionality.” Affected versions listed: 5.7.1 through 5.16.1.
We were not given any details - just the entire policy ref, with no indication of which part(s) we allegedly violated. We submitted an appeal right after receiving the email, but haven’t heard back yet, while the extension was delisted immediately.
I also attempted to reach out publicly via X, tagging both @firefox and @mozilla, and - again - received no response.
So my question is: What is the appropriate channel to actually get a reply, start a meaningful conversation, and resolve this issue in a reasonable timeframe?
We want to understand what Mozilla believes is problematic in the extension so we can address it - but we can’t fix what we aren’t told.
Any guidance on how to get an actual human response - or escalation path - would be appreciated.
Hey @superkalo, it sounds like your extension may have been incorrectly caught up in our anti-abuse efforts. As recent reporting has suggested, AMO is the target of an ongoing abuse campaign by crypto scammers. As our Add-ons Operations manager put it, “it’s a constant cat and mouse game” as malicious “developers try to work around our detection methods.”
The best channel is the appeal process. I realize that’s an underwhelming answer. I know it’s frustrating to be removed and not be able to do anything as you wait for your appeal to be processed, but we’re working through the appeal queue as quickly as we can.
Also, for future reference the @firefox and @mozilla accounts on X aren’t directly involved with Add-ons operations while the @mozamo is. That being said, I’m the main person monitoring that account and TBH I’m more active than on X.
The Ambire add-on is open source - the codebase is already on GitHub.
Shouldn’t that be enough? I’ve written one or two extensions, that are published on GitHub. I don’t use Chrome Web Store or Mozilla Add-Ons to upload the extensions I’ve written or download extensions. GitHub serves the same purpose without the politics.
Quickly after that, our extension was immediately disabled with only a generic “deceptive/fraudulent functionality” notice and a link to the entire policy document - no specifics.
We have now been waiting 6 days without clarification. Not resolution - just clarification. In that time, every Firefox user of ours sees this scary warning:
If this had happened to our primary user base - which thankfully is not on Firefox now - it would have been a complete disaster.
As it is, we’re already facing serious credibility damage. This is beyond unprofessional, and it’s making us seriously reconsider whether continuing Firefox support is worth the risk.
Given the impact on our users and our brand, I’d like to kindly ask you escalate our case for review.
Our extension has now been restored. Yesterday evening - 7 days after our appeal and request for clarification - Mozilla’s team responded, confirming that the original removal was incorrect.
The add-on is back online (previous affected versions remain disabled), and we’ve been asked to submit a new version for review.
Marking this issue as resolved.
We’ll now be working to repair the credibility impact from the past week. As feedback: if an immediate delisting is being considered in the future, opening a direct, timely conversation with the developer could prevent unnecessary disruption and help resolve issues much faster.
