Difference between revisions of "AutoRun"

From SpybotWiki
Jump to: navigation, search
(Description)
Line 2: Line 2:
  
 
==Usage==
 
==Usage==
  AutoRun:[value],[filename data],<advanced file parameters>
+
  AutoRun:<value name>,<filename data>[,advanced file parameters]
  
 
===Examples===
 
===Examples===
Line 14: Line 14:
 
# The first parameter specifies the name of the registry value to look for; this parameter can be used with [[AlgoPrefix|Algo-Prefixes]]. {{AlgoPrefix}}
 
# The first parameter specifies the name of the registry value to look for; this parameter can be used with [[AlgoPrefix|Algo-Prefixes]]. {{AlgoPrefix}}
 
# The second parameters takes a file path and name. It understands both [[AlgoPrefix|Algo-Prefixes]] and [[Path templates|path templates]]. {{AlgoPrefix}} {{PathTemplates}}
 
# The second parameters takes a file path and name. It understands both [[AlgoPrefix|Algo-Prefixes]] and [[Path templates|path templates]]. {{AlgoPrefix}} {{PathTemplates}}
# The third parameter allows you to specify [[Advanced file parameters|advanced file parameters]] to limit the scan to entries that point to files that have specific contents. Since file names can be misleading and ambiguous, it is highly recommend to specify them.
+
# The third parameter allows you to specify [[Advanced file parameters|advanced file parameters]] to limit the scan to entries that point to files that have specific contents. Since file names can be misleading and ambiguous, it is highly recommend to specify them. Also, a special advanced parameter [[flagifnofile]] can be used here, in case you specified advanced file parameters, but the associated file does not exist.
 +
 
 +
===Scan Results===
 +
* Any entries in ''Run'', ''RunServices'', ''RunOnce'' or ''RunServicesOnce'' (from ''\SOFTWARE\Microsoft\Windows\CurrentVersion\'' for both HKEY_LOCAL_MACHINE and all users) that are identified by both ''value name'' and ''filename data''.
 +
* The files associated with the entries, if they were found.
  
 
==See also==
 
==See also==
 +
* [[Advanced file parameters]]
 
* [[AlgoPrefix]]
 
* [[AlgoPrefix]]
* [[Advanced file parameters]]
 
 
* [[Path templates]]
 
* [[Path templates]]
 
* [[Description templates]]
 
* [[Description templates]]
Line 28: Line 32:
  
 
[[Category:SBI Commands]]
 
[[Category:SBI Commands]]
[[Category:SBI Commands (current)]]
 
 
[[Category:SBI Commands supporting AlgoPrefix]]
 
[[Category:SBI Commands supporting AlgoPrefix]]

Revision as of 09:22, 18 February 2008

Autorun helps you detect registrx autorun settings.

Usage

AutoRun:<value name>,<filename data>[,advanced file parameters]

Examples

AutoRun:"AdRoarUpdate","<$WINDIR>\ARUpdate.exe","filesize=86016,md5=5F45E52554D022A757BA637E4E03B0A5"

This example searches registry Run keys (global and for all users) for entries named AdRoarUpdate, pointing to a file ARUpdate.exe inside the Windows folder, that matches the specified advanced file parameters.

Description

This parameter takes two to three parameters, with the third one highly recommended.

  1. The first parameter specifies the name of the registry value to look for; this parameter can be used with Algo-Prefixes. AP
  2. The second parameters takes a file path and name. It understands both Algo-Prefixes and path templates. AP PT
  3. The third parameter allows you to specify advanced file parameters to limit the scan to entries that point to files that have specific contents. Since file names can be misleading and ambiguous, it is highly recommend to specify them. Also, a special advanced parameter flagifnofile can be used here, in case you specified advanced file parameters, but the associated file does not exist.

Scan Results

  • Any entries in Run, RunServices, RunOnce or RunServicesOnce (from \SOFTWARE\Microsoft\Windows\CurrentVersion\ for both HKEY_LOCAL_MACHINE and all users) that are identified by both value name and filename data.
  • The files associated with the entries, if they were found.

See also

Similar commands