BubbleLoader: ReversingLabs says patched WinRAR copies carry malware
Help Net Security reports ReversingLabs says BubbleLoader patches WinRAR and other programs; verify your WinRAR is the publisher’s copy.
- Published
- Ecosystem
- Desktops, browsers and mobile
- Exploitation
- Yes, according to ReversingLabs as reported by Help Net Security, which describes samples since February 2026 and two activity clusters in mid-September and early October; victims are not confirmed.
What happened
According to Help Net Security, ReversingLabs has analysed a loader called BubbleLoader that turns ordinary Windows programs into carriers for other malware. Help Net Security reports that ReversingLabs says the attackers rewrite a few instructions at a program’s entry point and add two PNG images that hold the hidden code. Help Net Security lists the known host programs as WinRAR, the x64dbg debugger, Windows Media Player, the Firefox launcher and virtiofs.
Help Net Security reports the following details, attributed to ReversingLabs:
- The earliest BubbleLoader samples appeared in February 2026. ReversingLabs tracked two clusters of activity, in mid-September and early October.
- Only the first PNG is a real image. The second starts with a valid PNG signature and then continues as encrypted code. Hidden code in it uses the bytes of the real image as a rolling XOR key to decrypt the next stage, which decrypts the final payload and loads it directly into memory.
- Because the real image contains long runs of zeros, parts of the loader sit unencrypted in the file. The fake image also shows a byte in the PNG width field that should be 0x00 but is 0x55 in the sample shown.
- The loader overwrites compiler filler bytes with values from the processor’s timestamp counter, so the payload’s in-memory hash differs on every run. Analysts recover the original by patching that loop out.
- The loader hooks RtlPcToFileHeader in Windows’ ntdll library and registers the payload’s exception table, giving the payload working error handling.
Not confirmed: Help Net Security says ReversingLabs does not state how the tampered programs reach victims, and the final payload varies from sample to sample. The article names no victims, no actor and no impact figures.
Am I affected?
The sources do not say how many systems are affected or how the altered programs are distributed. You could be affected if altered copies of the listed programs (WinRAR, x64dbg, Windows Media Player, the Firefox launcher, virtiofs) are present on your network. Help Net Security’s article does not say whether any particular release is altered. Its first suggested step is to make sure the WinRAR on your network is the copy its publisher shipped.
Help Net Security reports that ReversingLabs listed 24 SHA-256 hashes for BubbleLoader samples. These describe the patched programs on disk, not the payload, whose fingerprint changes on every run. The hash list itself is not reproduced in the article text available here, so it is not confirmed here.
What to do now
- Make sure the WinRAR on your network is the copy its publisher shipped. This is the first step Help Net Security gives.
- Apply strict application allowlisting and code-signing verification to catch altered binaries, as ReversingLabs recommends according to Help Net Security.
- Add alerts, per the same recommendations, for memory allocated as readable, writable and executable at once, and for protection changes aimed at ntdll’s exception routines.
- Add static rules that flag PNGs with truncated headers.
- Because payload hashes change from run to run, Help Net Security says ReversingLabs points responders toward behavior in memory and checks on each program’s entry point. The 24 published SHA-256 hashes only cover the patched programs on disk.