It depends on the attack vector. Typically you’re right, but malicious .lnk files are often paired with other malicious methods to infect machines. Sometimes they’re configured as a worm that copies and spreads when a flash drive is connected, sometimes they’re configured to download a remote payload when another script or program is started. The problem is that it’s a type of file that’s often overlooked because it seems innocent.
It isn’t necessarily the case that the Trojan needs to be interacted with by the user in order to execute the malicious code. Just having the file on your machine opens the door for all kinds of attacks (especially if you’re using a headless setup: you wouldn’t necessarily know you have the .lnk file in the system unless you’re manually unpacking your downloads yourself). All it needs is for another piece of infected code to run and look for that file, and it can open the door for more traditional malicious code.
It depends on the attack vector. Typically you’re right, but malicious .lnk files are often paired with other malicious methods to infect machines. Sometimes they’re configured as a worm that copies and spreads when a flash drive is connected, sometimes they’re configured to download a remote payload when another script or program is started. The problem is that it’s a type of file that’s often overlooked because it seems innocent.
It isn’t necessarily the case that the Trojan needs to be interacted with by the user in order to execute the malicious code. Just having the file on your machine opens the door for all kinds of attacks (especially if you’re using a headless setup: you wouldn’t necessarily know you have the .lnk file in the system unless you’re manually unpacking your downloads yourself). All it needs is for another piece of infected code to run and look for that file, and it can open the door for more traditional malicious code.