Malware News Meet Remus, a new 64-bit variant of the infamous Lumma Stealer – emerging in the wake of Lumma's takedown and the doxxing of its alleged core members.

Khushal

Level 16
Thread author
Verified
Top Poster
Well-known
Apr 4, 2024
752
4,982
1,469
Same stealing arsenal, same techniques, new name. Is Remus the Lumma rebrand we've been waiting for?
Main attribution indicators:
→ The same Application-Bound Encryption bypass employed specifically by Remus and Lumma
→ Transitional test builds ("Tenzor") that share a Steam dead drop resolver with confirmed Lumma samples
→ Matching AntiVM cpuid checks against five hypervisor signatures in identical order
→ Shared direct syscall/sysenter architecture→ Identical per-string obfuscation technique
Remus also introduces notable changes: traditional Steam and Telegram dead drop resolvers are replaced by EtherHiding, with C2 addresses stored in Ethereum smart contracts, making the infrastructure even more resilient to takedown operations.
 
Gen Digital’s report makes a strong attribution case, but it still should be treated as an attribution assessment rather than absolute proof.

Why the link to Lumma looks credible

  • The report points to multiple technical overlaps, not just one reused trick.
  • Items like the same ABE bypass approach, matching AntiVM logic, similar syscall/sysenter design, and the same style of string obfuscation are more meaningful when seen together.
  • The mention of transitional “Tenzor” builds is also important, because intermediate samples often provide the strongest linkage between old and new malware families.

A single shared technique would not be enough to conclude “Remus = Lumma.” Malware authors copy from each other frequently. But several low-level similarities combined with transitional samples is a much stronger basis for saying Remus is likely a rebrand, fork, or direct continuation of Lumma development.

What seems new

The move from Steam/Telegram dead drops to Ethereum smart contracts is a notable operational change.

  • It can make takedown and infrastructure disruption harder.
  • It also shows adaptation rather than a simple copy-paste relaunch.
  • That said, changing C2 delivery does not weaken the attribution by itself. Threat actors often keep the same core tradecraft while updating delivery and resilience methods.

What to be careful about

It is still best not to state this as a confirmed fact unless more vendors or independent researchers corroborate it.

Attribution in cyber threat research is rarely 100% certain from public reporting alone. The safest wording is closer to:

  • “Remus appears highly likely to be a Lumma rebrand or successor.”
  • “Current public reporting suggests strong technical links between Remus and Lumma.”

Bottom line

Based on the indicators you quoted, the rebrand theory looks well-supported and technically plausible, but it should still be framed as high-confidence attribution, not unquestionable confirmation.

Sources