There is still no detection on the client of this file. More than 3 days have passed since the definition appeared on VirusTotal. I take it that engine updates are more for eye wash, in fact signatures are not updated locally?
Yes, I sent this file using the link you suggested. But the status check did not give anything.
I rewrote the sample again. You can check the presence of the detector again.
The file detect is now available, arrived with the latest LiveUpdate updates. The other malicious scripts I mentioned earlier are now also detected with the Trojan Horse definition.
Did you submit file/s to Norton?
Thanks. I deleted cn.ps1 file....so, can't see detection my side.
The file detect is now available, arrived with the latest LiveUpdate updates. The other malicious scripts I mentioned earlier are now also detected with the Trojan Horse definition. In any case, it is at least some progress.
Script Control helps protect you from malware that you download or receive as attachments in phishing emails. It removes suspicious scripts from files and sanitizes the files, by default.
However, you can restore the original files with the script, and configure how you want Norton to handle documents with embedded scripts.
Scripts are used to make documents dynamic and interactive. Although the primary objective of scripts is to improve the document experience, cybercriminals can use them to sneak malware on your computer. Scripts are generally not important to the function of a document and many software programs disable them by default.
Script Control identifies potential threats based on the behavior of files. If Norton detects any potentially dangerous activity when you open a document with embedded script, it blocks the application from running the script. You can configure how you want Norton to handle the scripts when you open documents with embedded scripts.
Script Control helps protect you from malware that you download or receive as attachments in phishing emails. It removes suspicious scripts from files and sanitizes the files, by default. However, you can restore the original files with the script, and configure how you want Norton to handle documents with embedded scripts.
It’s interesting why Norton Script Control doesn’t remove it. I think this component doesn’t depends on virus signatures and should remove such viruses.
@uddu feels the file is Not detected by Norton.
Use this form to upload a suspected infected file which has not been detected by Norton. This is also called a False Negative.
Sorry, of course, but it's a shame! I check the malware scripts PowerShell one after the other, and no antivirus reaction! Signature databases are not updated locally, it's a fact! Is there any way you can comment on this?
uddu:
Why isn't there a detection on this malicious file on the client when the detection on VirusTotal has long since appeared?
Maybe, VirusTotal is reporting on running the PowerShell script file.
Maybe, ask VirusTotal > https://www.virustotal.com/gui/contact-us
Have you run the PowerShell script file.
@uddu feels the file is Not detecting by Norton.
Use this form to upload a suspected infected file which has not been detected by Norton. This is also called a False Negative.
Hi! I understand it all very well. I'm interested in another question, Why isn't there a detection on this malicious file on the client when the detection on VirusTotal has long since appeared?
On Windows 10, PowerShell is a command-line tool designed by Microsoft to run commands and scripts to change settings and automate tasks. In a way, it's similar to Command Prompt. However, PowerShell is a more capable command-line interface (CLI) that offers an extensive set of tools and more flexibility and control. Also, unlike Command Prompt, PowerShell is available on Windows, macOS, and Linux.
A script is just a collection of commands saved into a text file (using the special ".ps1" extension) that PowerShell understands and executes in sequence to perform different actions.
The only caveat is that the default security protocol always blocks any script from running on a device. This means that when double-clicking a ".ps1" file on Windows 10 nothing will happen, and if you try to run the script within PowerShell, you'll see the "cannot be loaded because running scripts is disabled on this system" error message. However, it's not impossible to run scripts on your computer. You only need to enable the correct execution policy.
A PowerShell script is really nothing more than a simpletext file. The file contains a series of PowerShell commands, with each command appearing on a separate line. For the text file to be treated as a PowerShell script, its filename needs to use the . PS1 extension.