Closed
Bug 952255
Opened 12 years ago
Closed 8 years ago
Malicious addon "YoutubeAdblocker" needs blocklisting
Categories
(Toolkit :: Blocklist Policy Requests, defect)
Toolkit
Blocklist Policy Requests
Tracking
()
RESOLVED
INVALID
People
(Reporter: mhammell, Assigned: jorgev)
References
Details
Attachments
(1 file)
1.56 KB,
application/octet-stream
|
Details |
Hello,
The attached zip contains a sample of a malicious addon. It hijacks a victim's Facebook account and sends spam to their friends.
Thanks!
Facebook Security
MD5: fdca911143ed2232c322922d0ac7c064
Assignee | ||
Comment 2•12 years ago
|
||
The attached add-on seems to be incomplete, and it doesn't appear to do anything. Please reopen this bug if you can provide the full XPI.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Flags: needinfo?(mhammell)
Resolution: --- → INCOMPLETE
![]() |
||
Comment 3•11 years ago
|
||
This add-on is being distributed with randomized IDs, and is currently one of our top search hijackers. I'm not sure where it comes from, or what it does, but combined with the above abuse report, I think we should block by name ASAP.
Status: RESOLVED → REOPENED
Ever confirmed: true
Flags: needinfo?(mhammell)
Resolution: INCOMPLETE → ---
Found a new one. Jorge, current status?
7tG@zEb.net youtubeadblocker 1.0
Flags: needinfo?(jorge)
ru@gfK0J.edu youtubeadblocker 1.0
Assignee | ||
Comment 6•11 years ago
|
||
We can't do the name block due to bug 1111728 (or at least we should wait for longer so usage of Firefox 28 and earlier isn't a factor).
I blocked those two IDs: https://addons.mozilla.org/en-US/firefox/blocked/i854, but I'll keep this bug open.
Flags: needinfo?(jorge)
Updated•10 years ago
|
Product: addons.mozilla.org → Toolkit
Assignee | ||
Comment 7•8 years ago
|
||
Closing old blocklist requests that shouldn't be valid after the move to WebExtensions-only in Firefox 57. Please comment if you think this bug is still valid and should be reopened.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 8 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•