A unknown addon in firefox addon store with 4.5+ rating.

(From, most of the comments it’s seems like this addon is suspicious and don’t have enough proof or evidence to trust it with our data. So please everyone avoid using this addon. A better one is “UBLOCK ORIGIN”).

  • tavu@sopuli.xyz
    link
    fedilink
    arrow-up
    13
    ·
    2 months ago

    If you’re using Mozilla’s level of endorsement as a metric, note this prominent disclaimer on the addon’s page:

    ⚠️ This add-on is not actively monitored for security by Mozilla. Make sure you trust it before installing.

      • lucasmz ∞@hachyderm.io
        link
        fedilink
        arrow-up
        3
        ·
        2 months ago

        @Alb087 @tavu yes, it doesn’t automatically mean it’s unsafe, but this is shady software none the less.

        I use a few extensions which also have this warning but I do because I trust them

        Pretty much everyone here is just recommending ublock origin, so just use that.

  • TFO Winder@lemmy.ml
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    2 months ago

    Check the licence.

    If it’s not any open source licence then fundamentally not trustable.

  • umami_wasabi@lemmy.ml
    link
    fedilink
    arrow-up
    6
    arrow-down
    4
    ·
    edit-2
    2 months ago

    I’m not going to tell you what to use instead, but how you make the judgement for yourself: audit the code yourself

    The source code is linked right there, and you don’t need trusting someone to make the call. You’re making the call. Mind you, the actual add-on installed from Mozilla Add-Ons might contains different code then what shown in the repo. I never release any add-ons so that is just a wild guess and a hint possibility this could happen.

    To give you an head start: look for URLs and any encoded strings in all files, be it Base64 or something else. And follow them to find out why there it is there, how is it triggered, etc. Same goes for encoded strings with the added question: what was encoded within.

    Still, that is just the basic, and I’m not too into JavaScript but there could be other ways of hiding information, like in an image file via steganography.

      • umami_wasabi@lemmy.ml
        link
        fedilink
        arrow-up
        2
        arrow-down
        2
        ·
        edit-2
        2 months ago

        Yes, but we are not auditing security or cryptography implementation.

        Instead, the goal is get a sense how it works, and look for suspicious codes or have if parts hidden (encoded) and doesn’t want people to know. That’s relatively way easier than a serious audit.