Run ImunifyAV from command line on a specific path

[scott]

Can you run ImunifyAV from the command line on a specific path and allow the process to stay in the foreground until it is finished and display a report?

Something like clamscan but with the ImunifyAV database.

[akots]

Hello Scott,

You can start an on-demand ImunifyAV scan for a specific path with:

imunify-antivirus malware on-demand start --path /home/<username>/public_html/

To review the scans that were started, you can use:

imunify-antivirus malware on-demand list

Then, once you have the relevant

SCAN_ID

, you can check the malware findings for that particular scan with:

imunify-antivirus malware malicious list --by-scan-id <SCAN_ID>

At the moment, the CLI is documented as separate subcommands for starting the scan, checking scan status/list, and then viewing malware results, rather than as a single clamscan-style foreground command that waits for completion and immediately prints the final report. The relevant commands documented are

malware on-demand start --path

,

malware on-demand list

,

malware on-demand status

, and

malware malicious list

, with -

-by-scan-id

available for filtering results.

[scott]

I think it'd be a great idea if

imunify-antivirus malware on-demand start --path /home/<username>/public_html/

gave the scan id of that scan, if a true foreground scanning system is not possible.

That way you can script it to run the command and then tell the script to watch for the completion of that scanid.

You can run that command and then immediately run

imunify-antivirus malware on-demand list

to see the latest/running scanid, but that's kind of a race condition, if another scan happens to start at the same time or the scan finishes before you can get the list.

Just my thoughts on it.

[scott]

Additionally, it'd be nice to be able to pass a file with a list of files to scan rather than just a path to scan.

This way you can utilize find to list files that have been modified within a certain amount of days (or whatever you want to find) and pass that list to imunifyav to be scanned.

[akots]

Hello Scott,

Thank you for the detailed suggestions! We really appreciate you taking the time to share them. Your feedback makes sense, especially for workflows where a more direct, foreground-style scan/report flow would be helpful.

This looks like a good candidate for a feature request. If you’d like, please submit it via our Feature Portal, as described here: https://features.imunify360.com/

You can find the instructions in this article:
https://cloudlinux.zendesk.com/hc/en-us/articles/5795005123740-How-to-submit-an-Imunify-feature-request