Closed Bug 1603731 Opened 3 years ago Closed 3 years ago

Extension block request: Add-ons using obfuscated code


(Toolkit :: Blocklist Policy Requests, task)

Not set





(Reporter: TheOne, Assigned: TheOne)


(Whiteboard: [extension])

Extension name Add-ons using obfuscated code
Extension versions affected <all versions>
Platforms affected <all platforms>
Block severity hard


I’ve reviewed the add-ons and found they use obfuscated code.

Extension GUIDs


The block has been pushed.

Group: blocklist-requests
Closed: 3 years ago
Resolution: --- → FIXED

Hello Mozilla Team,

This is Sebastian, the CTO of snapADDY.

I am contacting you regarding the blacklist of firefox addons, that was introduced in the last firefox update:
We assumed this would only apply for addons released in the official store, not for self-hosted extensions.

The code review process we remember from our time we released the app in the addon store would not be suiteable to us.
For one that our code base is now way more complex and as I remember it often took over a month till our addon got approved (we release a new version every 2 weeks)

Is there at least a way to disable the blacklist in the firefox config or something like that?
Is there an alternative way to establish the trust to not put our addon on the blacklist? The intention of our addon is not to spread malicious software or malware.
Our customers pay us directly for the use of the software and we are not secretly collecting data or selling ads.

We are a B2B SaaS application and a lot of our customers actually prefer firefox over chrome, with this new rule we will no longer be able to support those customers.

Best regards,
Sebastian Metzger

Flags: needinfo?(awagner)

Thank you, we will reply to the email you sent us.

Flags: needinfo?(awagner)
You need to log in before you can comment on or make changes to this bug.