Difference between revisions of "AutoRun"
(→Examples: updated md5 to make it more clear that this is an invented example only) |
m (→Examples: more generic) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 12: | Line 12: | ||
==Usage== | ==Usage== | ||
| − | AutoRun:<value | + | AutoRun:<value(string)>,<filename(string)>[,advanced file parameters] |
===Examples=== | ===Examples=== | ||
| − | AutoRun:" | + | AutoRun:"MalwareEntry","<$WINDIR>\MyMalware.exe","filesize=86016,md5=1234567890ABCDEFFEDCBA0987654321" |
| − | This example searches registry Run keys (global and for all users) for entries named '' | + | This example searches registry Run keys (global and for all users) for entries named ''MalwareEntry'', pointing to a file ''MyMalware.exe'' inside the Windows folder, that matches the specified [[Advanced file parameters|advanced file parameters]]. |
===Description=== | ===Description=== | ||
Latest revision as of 17:36, 23 February 2008
| AutoRun | |
| Group | Registry |
| Main Application | Version 1.4 or later |
| Required Update | n/a |
| File Parameters | yes (third) |
| Registry Parameters | no |
| Build Parameters | no |
| Special Parameters | flagifnofile |
Autorun helps you detect registry autorun settings.
Usage
AutoRun:<value(string)>,<filename(string)>[,advanced file parameters]
Examples
AutoRun:"MalwareEntry","<$WINDIR>\MyMalware.exe","filesize=86016,md5=1234567890ABCDEFFEDCBA0987654321"
This example searches registry Run keys (global and for all users) for entries named MalwareEntry, pointing to a file MyMalware.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.
- The first parameter specifies the name of the registry value to look for; this parameter can be used with Algo-Prefixes. AP
- The second parameters takes a file path and name. It understands both Algo-Prefixes and path templates. AP PT
- 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.
