← Latest papers
💻 computer science

A Decompilation-Driven Framework for Malware Detection with Large Language Models

This paper presents a decompilation-driven framework that uses Large Language Models to classify malware, demonstrating that while fine-tuned models significantly outperform standard ones, they still require continuous retraining to effectively detect evolving threats and cannot yet replace traditional antivirus solutions.

Original authors: Aniesh Chawla, Udbhav Prasad

Published 2026-01-15
📖 4 min read☕ Coffee break read

Original authors: Aniesh Chawla, Udbhav Prasad

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are a security guard at a very busy airport. Your job is to look at every suitcase (a computer file) and decide: "Is this safe, or is it a bomb?"

Traditionally, guards use a checklist. If a suitcase has a specific lock, a certain weight, or a known brand of zipper, they flag it. This works great for known bombs. But what if a criminal builds a brand-new bomb using a different lock, a new material, and a strange shape? The checklist fails because the bomb doesn't look like anything on the list.

This paper is about trying a new kind of guard: an AI detective (a Large Language Model, or LLM) that doesn't just check a list, but actually reads the instructions inside the suitcase to understand what it's trying to do.

Here is how the researchers tested this idea, broken down simply:

1. The Translation Problem

Computer viruses (malware) are written in "machine code," which looks like gibberish to humans and even to most AI. It's like trying to read a book written in a secret, scrambled language.

To fix this, the researchers used a tool called Ghidra. Think of Ghidra as a super-smart translator. It takes the scrambled machine code and translates it into C code (a standard programming language that humans and AI can read). Now, instead of looking at gibberish, the AI detective is reading a story written in plain English (well, code-English).

2. The Two Tests

The researchers put their AI detectives through two different exams:

  • Test A: The "Old School" Exam (2017 Data)
    They gave the AI a pile of old viruses and safe files from 2017.

    • The Result: The AI was okay, but not amazing. It got about 80% right.
    • The Comparison: They also used a traditional "checklist" computer program (XGBoost). That old-school program got 98.5% right.
    • The Lesson: On old, familiar threats, the traditional checklist is still the king. The AI detective was a bit confused by the noise.
  • Test B: The "New Threat" Exam (2025 Data)
    They gave the AI a fresh pile of brand-new viruses and safe files from 2025.

    • The Result: The "off-the-shelf" AI detective got confused and dropped to 64% accuracy. It couldn't recognize the new tricks the criminals were using.
    • The Twist: The researchers then gave the AI a "crash course" (called fine-tuning). They fed it a small, curated list of examples specifically designed to teach it the difference between good and bad code.
    • The Outcome: After this crash course, the AI detective jumped to 83% accuracy. It was now better than the traditional checklist (which dropped to 74% because it didn't know the new tricks).

3. The Big Catch

The paper makes one very important point: The AI is not a magic bullet yet.

Even the "crash-course" AI started to struggle when faced with newer threats it hadn't seen before. It's like a student who memorized the answers to last year's test but gets stumped when the teacher changes the questions slightly.

The researchers found that to keep the AI working, you can't just train it once and forget it. You have to constantly feed it new examples of bad guys as they appear. If you don't keep updating its "education," it becomes useless against new threats.

4. The Limitations (Why it's not perfect yet)

The paper points out a few hurdles:

  • The "Too Long" Problem: Some files are so huge that the AI's "memory" (context window) gets full. It starts reading the beginning of the story, forgets the middle, and misses the important clues at the end.
  • The "Black Box" Problem: Sometimes the AI says "This is a virus," but it can't clearly explain why. In security, you need to know the reason to trust the decision.
  • The "Fake Out" Problem: Some safe files (like system drivers) look very similar to viruses because they do similar low-level work. The AI sometimes gets tricked by these "imposters."

The Bottom Line

This paper shows that using AI to read the "story" inside a computer file is a promising new way to catch viruses, especially the new, sneaky ones that old checklists miss.

However, the AI isn't ready to replace human security guards or traditional antivirus software just yet. It needs constant training (like a student who never stops studying) to stay sharp. If we keep feeding it new examples of bad code, it might one day become the gold standard for keeping our computers safe.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →