DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Zones

Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Generative AI has transformed nearly every industry. How can you leverage GenAI to improve your productivity and efficiency?

SBOMs are essential to circumventing software supply chain attacks, and they provide visibility into various software components.

Related

  • AI-Powered Ransomware and Malware Detection in Cloud Environments
  • CRITICAL_PROCESS_DIED: How to Fix This Windows Blue Screen Error
  • Why 99% Accuracy Isn't Good Enough: The Reality of ML Malware Detection
  • Evaluating Similariy Digests: A Study of TLSH, ssdeep, and sdhash Against Common File Modifications

Trending

  • Testing Java Applications With WireMock and Spring Boot
  • Understanding k-NN Search in Elasticsearch
  • Stop Building Monolithic AI Brains, Build a Specialist Team Instead
  • Breaking Free from ZooKeeper: Why Kafka’s KRaft Mode Matters
  1. DZone
  2. Software Design and Architecture
  3. Security
  4. These Packers Are Not From Wisconsin

These Packers Are Not From Wisconsin

Sorry Green Bay, we're actually talking about the method cyberattackers use to hide or obfuscate malware when attacking a system.

By 
Christopher Lamb user avatar
Christopher Lamb
·
Jul. 21, 17 · Analysis
Likes (1)
Comment
Save
Tweet
Share
1.9K Views

Join the DZone community and get the full member experience.

Join For Free

Malware uses a wide variety of techniques to stay hidden or obfuscated, or otherwise, make malware analyst's lives more difficult. One of the techniques they use is payload packing.

Now, packers, as they're called, have been around forever. They were originally designed years ago to compress software that was delivered over modems. There's a wide variety of them, including custom variants, in the wild today. One of the most popular packers today is UPX.

Why use them? Well, if you're a malware author, you want to make life as difficult as you can for malware analysts - you know, the guys that develop malware signatures, figure out how to clean systems of your malware, that kind of thing? And packers are one way to do that (though today, it's really more of an annoyance than a show-stopper most of the time).

By using a packer, you limit the amount of malware analysis someone can do on a static program image. Most of the time, with programs that aren't protected with some kind of obfuscation, it's trivial to load them into a disassembler or decompiler and get some idea of what the program does. We'll search for strings in the file. Look at the imported library functions. Examine function names - those kinds of things. But all these require a readable program, which you don't have if it's packed.

A packer works, essentially, by compressing the code and potentially the data sections of a program (you can compress other segments too, no reason why you couldn't) and then inserting the compressed information into another section in the executable. The packer will then usually insert a very simple, small section of code into the program image that will run when the file is executed. This code will just expand the compressed program into a program section and then transfer control to the expanded code.

When you look into a packed program with a disassembler, for example, you may only see two or three function calls and maybe a few library calls - not nearly enough for any useful program. But after you expand the program? Well, then you can see the entire payload and can understand exactly what it does. But expanding that code is not always as easy as you'd like. Sometimes, you can use utilities that will extract the compressed code and create a new executable. Other times, you need to use a debugger to step through the program, stopping and saving the program image immediately after decompression. Not as easy as it sounds if the program is using anti-debugging techniques.

Packers are useful for everybody after all - including malware authors. Not so much for malware analysts.

Malware

Opinions expressed by DZone contributors are their own.

Related

  • AI-Powered Ransomware and Malware Detection in Cloud Environments
  • CRITICAL_PROCESS_DIED: How to Fix This Windows Blue Screen Error
  • Why 99% Accuracy Isn't Good Enough: The Reality of ML Malware Detection
  • Evaluating Similariy Digests: A Study of TLSH, ssdeep, and sdhash Against Common File Modifications

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

ABOUT US

  • About DZone
  • Support and feedback
  • Community research
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • [email protected]

Let's be friends: