Win32/Packed.Obsidium.EJ

Spectating the Win32/Packed.Obsidium.EJ detection name means that your system is in big danger. This virus can correctly be identified as ransomware – sort of malware which encrypts your files and forces you to pay for their decryption. Deleteing it requires some specific steps that must be taken as soon as possible.

Win32/Packed.Obsidium.EJ detection is a malware detection you can spectate in your computer. It usually appears after the provoking actions on your computer – opening the dubious email messages, clicking the banner in the Web or installing the program from untrustworthy resources. From the moment it shows up, you have a short time to act until it begins its destructive action. And be sure – it is better not to await these harmful effects.

What is Win32/Packed.Obsidium.EJ virus?

Win32/Packed.Obsidium.EJ is ransomware-type malware. It searches for the files on your disk, encrypts it, and after that asks you to pay the ransom for getting the decryption key. Besides making your documents locked, this malware also does a lot of harm to your system. It modifies the networking setups in order to prevent you from looking for the elimination guidelines or downloading the anti-malware program. In some cases, Win32/Packed.Obsidium.EJ can additionally prevent the setup of anti-malware programs.

Win32/Packed.Obsidium.EJ Summary

In summary, Win32/Packed.Obsidium.EJ malware activities in the infected system are next:

  • Behavioural detection: Executable code extraction – unpacking;
  • SetUnhandledExceptionFilter detected (possible anti-debug);
  • Yara rule detections observed from a process memory dump/dropped files/CAPE;
  • Creates RWX memory;
  • Possible date expiration check, exits too soon after checking local time;
  • Dynamic (imported) function loading detected;
  • Reads data out of its own binary image;
  • CAPE extracted potentially suspicious content;
  • The binary contains an unknown PE section name indicative of packing;
  • The binary likely contains encrypted or compressed data.;
  • Authenticode signature is invalid;
  • Anomalous binary characteristics;
  • Encrypting the documents kept on the victim’s disk — so the victim cannot open these files;
  • Blocking the launching of .exe files of anti-malware programs
  • Blocking the launching of installation files of anti-virus programs

Ransomware has been a nightmare for the last 4 years. It is difficult to imagine a more hazardous malware for both individuals and organizations. The algorithms utilized in Win32/Packed.Obsidium.EJ (generally, RHA-1028 or AES-256) are not hackable – with minor exclusions. To hack it with a brute force, you need to have more time than our galaxy currently exists, and possibly will exist. But that virus does not do all these horrible things without delay – it can take up to a few hours to cipher all of your files. Hence, seeing the Win32/Packed.Obsidium.EJ detection is a clear signal that you must start the clearing procedure.

Where did I get the Win32/Packed.Obsidium.EJ?

Standard tactics of Win32/Packed.Obsidium.EJ injection are standard for all other ransomware examples. Those are one-day landing sites where users are offered to download and install the free app, so-called bait e-mails and hacktools. Bait emails are a pretty new method in malware distribution – you receive the email that simulates some routine notifications about shippings or bank service conditions changes. Inside of the e-mail, there is a malicious MS Office file, or a web link which leads to the exploit landing page.

Malicious email spam

Malicious email message. This one tricks you to open the phishing website.

Preventing it looks fairly uncomplicated, but still demands tons of recognition. Malware can hide in various places, and it is much better to stop it even before it goes into your PC than to depend on an anti-malware program. Essential cybersecurity awareness is just an important thing in the modern-day world, even if your interaction with a PC stays on YouTube videos. That can save you a lot of money and time which you would certainly spend while trying to find a fix guide.

Win32/Packed.Obsidium.EJ malware technical details

File Info:

name: 9347AE38D81D9B269186.mlwpath: /opt/CAPEv2/storage/binaries/93c8b476a7b6619d3de9c75c22718ff3db5c9bd579eae5633d7930ef7668bfbecrc32: DAF24A8Dmd5: 9347ae38d81d9b269186a29a2c147258sha1: f3ffe22170aed085773f04305d5e82d78517e368sha256: 93c8b476a7b6619d3de9c75c22718ff3db5c9bd579eae5633d7930ef7668bfbesha512: b8b9f1e714204516945d643c5bd4e8f1bf52bdae5f765ea92d2d0708e6424422220318d4345668133adcc5457b18d2302325ca985691389a9d0ade1ec55e35f8ssdeep: 12288:vGMHy87sn889kUcZHfioLvJWJeL9q1qTJKtG9hnqkkhBzlNHp84niXzx6:Oq729eNKotWUkqagmBZUttype: PE32 executable (GUI) Intel 80386, for MS Windowstlsh: T1E9E422CB8BD5CE73EC0C17B9E2838340BB71E4A867872753555116327E673A1DC6A6D0sha3_384: bfe13f19d2c88be1d2319cd46cee4cbfdce288c99c26bf5aba5b1e5a387eeeef78d66efb64f3b93d2a7f897bd36a6b20ep_bytes: eb05699404973250eb05d0aefe7b01e8timestamp: 2022-01-13 10:06:46

Version Info:

0: [No Data]

Win32/Packed.Obsidium.EJ also known as:

Bkav W32.AIDetect.malware2
Lionic Trojan.Win32.Convagent.3!c
Elastic malicious (high confidence)
MicroWorld-eScan Trojan.GenericKD.38534143
FireEye Generic.mg.9347ae38d81d9b26
ALYac Trojan.GenericKD.38534143
Cylance Unsafe
Sangfor Infostealer.MSIL.Stealer.bt
K7AntiVirus Trojan ( 0058cfd71 )
Alibaba TrojanPSW:MSIL/Stealer.9cc82dad
K7GW Trojan ( 0058cfd71 )
Cybereason malicious.170aed
Symantec ML.Attribute.HighConfidence
ESET-NOD32 a variant of Win32/Packed.Obsidium.EJ
APEX Malicious
Paloalto generic.ml
Kaspersky Trojan-PSW.MSIL.Stealer.bt
BitDefender Trojan.GenericKD.38534143
Avast Win32:Trojan-gen
Ad-Aware Trojan.GenericKD.38534143
Emsisoft Trojan.GenericKD.38534143 (B)
Zillya Trojan.Stealer.Win32.21365
TrendMicro TROJ_GEN.R067C0PAJ22
McAfee-GW-Edition BehavesLike.Win32.Vundo.jc
Sophos Mal/Generic-S
Ikarus Trojan.SuspectCRC
GData Trojan.GenericKD.38534143
Microsoft Trojan:Win32/Sabsik.FL.B!ml
Cynet Malicious (score: 100)
AhnLab-V3 Trojan/Win.Muldown.C4918206
McAfee RDN/Generic PWS.y
MAX malware (ai score=88)
VBA32 TScope.Malware-Cryptor.SB
Malwarebytes Trojan.MalPack
TrendMicro-HouseCall TROJ_GEN.R067C0PAJ22
Rising Exploit.ShellCode!8.2A (CLOUD)
SentinelOne Static AI – Malicious PE
MaxSecure Trojan.Malware.300983.susgen
Fortinet W32/PossibleThreat
BitDefenderTheta Gen:NN.ZexaF.34160.OuX@aWQbfwb
AVG Win32:Trojan-gen
Panda Trj/Genetic.gen

How to remove Win32/Packed.Obsidium.EJ?

About the author

Robert Bailey

Security engineer focused on malware behavior, removal workflows, and Windows hardening. Robert reviews threat articles for practical accuracy, checking detection names, symptoms, and cleanup steps before publication.

Leave a Comment