Closed
Bug 1148250
Opened 11 years ago
Closed 8 years ago
Suspicious Add-on XPI
Categories
(Toolkit :: Blocklist Policy Requests, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: tdowner, Unassigned)
Details
Attachments
(1 file)
|
66.06 KB,
application/x-xpinstall
|
Details |
A SUMO Helper found this add-on, {a50cec4a-6ecf-46a3-aef9-771c91b652cf}.xpi in his Firefox install. The SUMO helper looked through the xpi and found:
File; AddonObserver.js
AddonObserver.prototype.installPrepare = function(Instruction) {
//console.log("install");
//utils.installXpiFromUrl(Instruction.xpiUrl);
console.log("installPrepare", Instruction);
var tmpNsIFile = FileUtils.getFile("TmpD", [Math.random() + ".xpi"]); console.log(tmpNsIFile); ===>> // fuck off utils.downloadFile(Instruction.xpiUrl, tmpNsIFile); console.log(tmpNsIFile);
File; Console.js
// most recent window for using firebug // populated by xpcom window-mediator mrw: null // while mrw is null, save messages, to send them then , firebugQueue: []
and
// try to get ref to Firebug of very first FF window
I'm asking for a copy of the xpi. He isn't sure how it got on his machine.
| Reporter | ||
Comment 1•11 years ago
|
||
xpi: https://pastebin.mozilla.org/8827373
Not actually sure what it's doing
Comment 2•11 years ago
|
||
Do you have the actual XPI file? Pastebin isn't ideal to read the code.
Flags: needinfo?(tdowner)
| Reporter | ||
Comment 3•11 years ago
|
||
Flags: needinfo?(tdowner)
| Assignee | ||
Updated•10 years ago
|
Product: addons.mozilla.org → Toolkit
Comment 4•9 years ago
|
||
Ran a quick search on the updateURL mentioned in the install.rdf:
https://bw9210.virtualcloudnow.com/addon/firefox/update.rdf?guid=%ITEM_ID%&version=%ITEM_VERSION%
The same URL is mentioned in Bug 1161259 so they are probably related.
Comment 5•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: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•