The EICAR Anti-Virus Test File^[1] or EICAR test file is a computer file that was developed by the European Institute for Computer Antivirus Research (EICAR) and Computer Antivirus Research Organization (CARO) to test the response of computer antivirus (AV) programs.^[2] Instead of using real malware, which could cause real damage, this test file allows people to test anti-virus software without having to use a real computer virus.^[3]

Anti-virus programmers set the EICAR string as a verified virus, similar to other identified signatures. A compliant virus scanner, when detecting the file, will respond in more or less the same manner as if it found a harmful virus. Not all virus scanners are compliant, and may not detect the file even when they are correctly configured. Neither the way in which the file is detected nor the wording with which it is flagged are standardized, and may differ from the way in which real malware is flagged, but should prevent it from executing as long as it meets the strict specification set by European Institute for Computer Antivirus Research.^[4]

The use of the EICAR test string can be more versatile than straightforward detection: a file containing the EICAR test string can be compressed or archived, and then the antivirus software can be run to see whether it can detect the test string in the compressed file. Many of the AMTSO Feature Settings Checks^[5] are based on the EICAR test string.^[5]

The file is a text file of between 68 and 128 bytes^[6] that is a legitimate .com executable file (plain x86 machine code) that can be run by MS-DOS, some work-alikes, and its successors OS/2 and Windows (except for 64-bit due to 16-bit limitations). The EICAR test file will print "EICAR-STANDARD-ANTIVIRUS-TEST-FILE!" when executed and then will stop. The test string was written by noted anti-virus researchers Padgett Peterson and Paul Ducklin and engineered to consist of ASCII human-readable characters, easily created using a standard computer keyboard.^[7] It makes use of self-modifying code to work around technical issues that this constraint imposes on the execution of the test string.^[8]

The EICAR test string^[9] reads^[10]

X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*

The third character is the capital letter 'O', not the digit zero.

The string's hash values (68 bytes without any trailing newline character) are as follows:

According to EICAR's specification the antivirus detects the test file only if it starts with the 68-byte test string and is not more than 128 bytes long. As a result antiviruses are not expected to raise an alarm on some other document containing the test string.^[11] The test file can still be used for some malicious purposes, exploiting the reaction from the antivirus software:

• A race condition involving symlinks can cause antiviruses to delete themselves.^[12]
• A QR-encoded EICAR test file crashes some CCTV systems.^{[13][failed verification]}

• GTUBE – a similar test for unsolicited bulk email (email spam)