BrowserHelper - Revision history

CCRDude: /* Scan Results */ minor typo "toolbat"

2008-02-28T18:47:06Z

Scan Results: minor typo "toolbat"

← Older revision		Revision as of 18:47, 28 February 2008
Line 39:		Line 39:

	===Scan Results===		===Scan Results===
	* The BHO/toolbar registry entry identified by the first parameter; or a BHO/~~toolbat~~ registry associated with the CLSID identified by the first parameter.		* The BHO/toolbar registry entry identified by the first parameter; or a BHO/toolbar registry associated with the CLSID identified by the first parameter.
	* If the first parameter identifies a CLSID, the CLSID in addition to the associated BHO.		* If the first parameter identifies a CLSID, the CLSID in addition to the associated BHO.

CCRDude: /* Usage */ added var types

2008-02-22T15:54:27Z

Usage: added var types

← Older revision		Revision as of 15:54, 22 February 2008
Line 12:		Line 12:

	==Usage==		==Usage==
	BrowserHelper:<bho or clsid name>[,advanced file parameters]		BrowserHelper:<bho-name/clsid-name(string)>[,advanced file parameters]

	===Examples===		===Examples===

CCRDude: added "or later" to version

2008-02-22T13:41:56Z

added "or later" to version

← Older revision		Revision as of 13:41, 22 February 2008
Line 2:		Line 2:
	\|SYNTAX = BrowserHelper		\|SYNTAX = BrowserHelper
	\|PENAME = SpybotSD.exe		\|PENAME = SpybotSD.exe
	\|PEVERSION = 1.3		\|PEVERSION = 1.3 or later
	\|GROUP = Registry		\|GROUP = Registry
	\|MINUPDATE = n/a		\|MINUPDATE = n/a

CCRDude: fixed index of params in info box

2008-02-22T13:38:22Z

fixed index of params in info box

← Older revision		Revision as of 13:38, 22 February 2008
Line 5:		Line 5:
	\|GROUP = Registry		\|GROUP = Registry
	\|MINUPDATE = n/a		\|MINUPDATE = n/a
	\|ADVFILEPARAMS = yes (~~third~~)		\|ADVFILEPARAMS = yes (second)
	\|ADVREGPARAMS = no		\|ADVREGPARAMS = no
	\|ADVBUILDPARAMS = yes (~~third~~)		\|ADVBUILDPARAMS = yes (second)
	\|ADVSPECIALPARAMS = [[flagfile]]<br />[[flagifnofile]]		\|ADVSPECIALPARAMS = [[flagfile]]<br />[[flagifnofile]]
	}}The most common way spy- and adware links into Internet Explorer is creating a browser helper object.		}}The most common way spy- and adware links into Internet Explorer is creating a browser helper object.

CCRDude: added info box

2008-02-22T13:37:13Z

added info box

← Older revision		Revision as of 13:37, 22 February 2008
Line 1:		Line 1:
	The most common way spy- and adware links into Internet Explorer is creating a browser helper object.		{{SbiCmdInfo
			\|SYNTAX = BrowserHelper
			\|PENAME = SpybotSD.exe
			\|PEVERSION = 1.3
			\|GROUP = Registry
			\|MINUPDATE = n/a
			\|ADVFILEPARAMS = yes (third)
			\|ADVREGPARAMS = no
			\|ADVBUILDPARAMS = yes (third)
			\|ADVSPECIALPARAMS = [[flagfile]]<br />[[flagifnofile]]
			}}The most common way spy- and adware links into Internet Explorer is creating a browser helper object.

	==Usage==		==Usage==

CCRDude at 09:53, 18 February 2008

2008-02-18T09:53:57Z

← Older revision		Revision as of 09:53, 18 February 2008
Line 2:		Line 2:

	==Usage==		==Usage==
	BrowserHelper:[~~name]~~,<advanced file parameters>		BrowserHelper:<bho or clsid name>[,advanced file parameters]

	===Examples===		===Examples===
Line 21:		Line 21:
	While using [[RegyKey]] might be more fitting for just matching a browser helper object with a static name, you might encounter situations where a random name requires you to use the name of the associated class, or properties of the file the browser helper points to.		While using [[RegyKey]] might be more fitting for just matching a browser helper object with a static name, you might encounter situations where a random name requires you to use the name of the associated class, or properties of the file the browser helper points to.

	# The first parameter can identify both the BHO name, or the name of the class associated with the BHO.		# The first parameter can identify both the BHO name, or the name of the class associated with the BHO. You may use the wildcard ''*'' (use with care) if you specify [[Advanced file parameters\|advanced file parameters]] for the CLSID related InprocServer32. [[AlgoPrefix\|Algo-Prefixes]] are supported only after 1.5.2. {{AlgoPrefix}}
	# The second parameter, though optional, is highly recommended to refine the scan to be limited to BHO that point to a to be identified file, where the filename is gathered from the CLSID associated with the BHO.		# The second parameter, though optional, is highly recommended to refine the scan to be limited to BHO that point to a to be identified file, where the filename is gathered from the CLSID associated with the BHO.

	Important to point out is that while this is actually named after BHOs, it also detects Internet Explorer toolbars and Windows Explorer toolbars.		Important to point out is that while this is actually named after BHOs, it also detects Internet Explorer toolbars and Windows Explorer toolbars.

			If you want to catch the associated file as well, you need to use [[BrowserHelperEx]].

			===Scan Results===
			* The BHO/toolbar registry entry identified by the first parameter; or a BHO/toolbat registry associated with the CLSID identified by the first parameter.
			* If the first parameter identifies a CLSID, the CLSID in addition to the associated BHO.

	==See also==		==See also==
	* [[Advanced file parameters]]		* [[Advanced file parameters]]
			* [[AlgoPrefix]]

	===Similar commands===		===Similar commands===
Line 35:		Line 42:

	[[Category:SBI Commands]]		[[Category:SBI Commands]]
	[[Category:SBI Commands ~~(current)~~]]		[[Category:SBI Commands supporting AlgoPrefix]]

CCRDude: /* Description */

2008-02-17T16:41:37Z

Description

← Older revision		Revision as of 16:41, 17 February 2008
Line 20:		Line 20:
	===Description===		===Description===
	While using [[RegyKey]] might be more fitting for just matching a browser helper object with a static name, you might encounter situations where a random name requires you to use the name of the associated class, or properties of the file the browser helper points to.		While using [[RegyKey]] might be more fitting for just matching a browser helper object with a static name, you might encounter situations where a random name requires you to use the name of the associated class, or properties of the file the browser helper points to.

	# The first parameter can identify both the BHO name, or the name of the class associated with the BHO.		# The first parameter can identify both the BHO name, or the name of the class associated with the BHO.
	# The second parameter, though optional, is highly recommended to refine the scan to be limited to BHO that point to a to be identified file, where the filename is gathered from the CLSID associated with the BHO.		# The second parameter, though optional, is highly recommended to refine the scan to be limited to BHO that point to a to be identified file, where the filename is gathered from the CLSID associated with the BHO.

			Important to point out is that while this is actually named after BHOs, it also detects Internet Explorer toolbars and Windows Explorer toolbars.

	==See also==		==See also==

CCRDude: New page: The most common way spy- and adware links into Internet Explorer is creating a browser helper object. ==Usage== BrowserHelper:[name], ===Examples=== BrowserHe...

2008-02-16T14:35:32Z

New page: The most common way spy- and adware links into Internet Explorer is creating a browser helper object. ==Usage== BrowserHelper:[name],<advanced file parameters> ===Examples=== BrowserHe...

New page

The most common way spy- and adware links into Internet Explorer is creating a browser helper object.

==Usage==
BrowserHelper:[name],<advanced file parameters>

===Examples===
BrowserHelper:"abadbadBHO"
BrowserHelper:"Dummy spyware browser helper"

The first one would detect the following browser helper object:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\explorer\Browser Helper Objects\{12345678-ABCD-EFAB-CDEF-909876543210}]
@="abadbadBHO"

As for the second example, it detects the browser helper using the class name, identifying these two entries:

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\explorer\Browser Helper Objects\{12345678-ABCD-EFAB-CDEF-909876543210}]
[HKEY_CLASSES_ROOT\CLSID\{12345678-ABCD-EFAB-CDEF-909876543210}]
@="Dummy spyware browser helper"

===Description===
While using [[RegyKey]] might be more fitting for just matching a browser helper object with a static name, you might encounter situations where a random name requires you to use the name of the associated class, or properties of the file the browser helper points to.
# The first parameter can identify both the BHO name, or the name of the class associated with the BHO.
# The second parameter, though optional, is highly recommended to refine the scan to be limited to BHO that point to a to be identified file, where the filename is gathered from the CLSID associated with the BHO.

==See also==
* [[Advanced file parameters]]

===Similar commands===
* [[BrowserHelperEx]]
* [[IEExtension]]
* [[IELinks]]

[[Category:SBI Commands]]
[[Category:SBI Commands (current)]]