{"id":7853,"date":"2024-05-23T11:01:26","date_gmt":"2024-05-23T11:01:26","guid":{"rendered":"\/cybersecurity-blog\/?p=7853"},"modified":"2025-05-05T10:32:31","modified_gmt":"2025-05-05T10:32:31","slug":"malicious-scripts","status":"publish","type":"post","link":"\/cybersecurity-blog\/malicious-scripts\/","title":{"rendered":"Malicious Scripts: Examples and Analysis in ANY.RUN"},"content":{"rendered":"\n

When we talk about traditional malware, we’re usually referring to compiled malware<\/strong>. This means that the malware\u2019s source code is translated into machine language. <\/p>\n\n\n\n

Compilation happens when the computer takes human-readable code and converts it into instructions that the processor can understand, creating static files. For instance, it compiles C<\/strong> or C++ <\/strong>code into executable files like .exe<\/strong> or .dll <\/strong>for Windows. <\/p>\n\n\n\n

The first compiled malware, called Brain, was created way back in 1986. That’s ancient history in the world of information technology! Over the years, we’ve become very good at detecting this type of threat. <\/p>\n\n\n\n

YARA rules <\/strong>and Signatures <\/strong>can be incredibly effective at spotting malicious code in executables. <\/p>\n\n\n\n

This doesn’t mean that compiled malware has become obsolete. Mirai<\/a> (written in C) and FormBook<\/a> (written in C++) are 3 examples of modern threats that fall into this bucket. But it has led attackers to invent something new. <\/p>\n\n\n\n

Enter malicious scripts and script-based malware<\/strong>. <\/p>\n\n\n\n\n

\n\n

\nEasily analyze compiled and script-based malware
in ANY.RUN<\/span> \n<\/p>\n\n\nCreate free account\n<\/a>\n<\/div>\n\n\n\n