Is heavy-fist.asi safe?
Nineteen of 75 engines flag this unsigned, packed DLL, including two tier-1 detectors, but generic labels and unconfirmed runtime behavior leave attribution unresolved.
The strongest concern is the combination of 19/75 detections, two independent tier-1 flags, unsigned code, and UPX-like high-entropy packing. However, the tier-1 labels are generic, one sandbox run did not confirm harmful activity, and the file has broad multi-year prevalence, so the evidence does not establish a specific malware family.
1cd60d7120423b53c8…f3447f635ad489Recommended next actions
Before opening
Do not open it until the source can be verified independently.
If you already opened it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
The strongest concern is the combination of 19/75 detections, two independent tier-1 flags, unsigned code, and UPX-like high-entropy packing. However, the tier-1 labels are generic, one sandbox run did not confirm harmful activity, and the file has broad multi-year prevalence, so the evidence does not establish a specific malware family.
Nineteen of 75 engines detected the DLL, including Fortinet and Symantec as two independent tier-1 signals. Their labels are generic, and there is no strong tier-1 family consensus tying the sample to Chgt, Lazy, or another named family. Static analysis shows an unsigned DLL with likely packing and a UPX1 section entropy of 7.99, which raises concern when combined with the detections. One completed sandbox run observed ambient techniques but no offensive techniques, persistence, malicious sandbox verdict, or confirmed malicious child. The file has also circulated widely since 2022, while 15 tier-1 engines remained silent, leaving a meaningful false-positive possibility. No complete contacted-host reputation result is available, although the sandbox recorded no network contacts.
What We Detected
19 of 75 antivirus engines flagged the DLL. Fortinet reported W32/PossibleThreat and Symantec reported ML.Attribute.HighConfidence, giving two independent tier-1 detections, while Panda used the Chgt name and several other engines supplied generic trojan or machine-learning labels. The differing labels do not form a strong family consensus.
Threat Behavior
The DLL is unsigned and appears packed; peAnalysis.likelyPacked=true and the UPX1 section has entropy 7.99. One sandbox run recorded nine ambient MITRE techniques, including T1027 and T1497, but behaviour.offensiveCount=0 and behaviour.hasMaliciousSandboxVerdict=false. No persistence indicators were recorded, and none of nine inspected children was confirmed malicious, although all child verdicts remain unresolved. The run recorded no network contacts, and contactedHosts=null means no separate host-reputation check was completed or saved.
What To Do Now
Do not load this ASI/DLL into a game or application unless its origin and expected hash can be verified from the official mod or software publisher. Keep endpoint protection enabled, quarantine the file for now, and replace it with a verified copy if provenance cannot be established.
Where this verdict could be wrong5 caveats
- 15 of 17 tier-1 engines did not detect the file, including Avast, BitDefender, ESET-NOD32, and F-Secure.
- The completed sandbox run produced no malicious sandbox verdict, no offensive techniques, and no persistence indicators.
- externalIntel.yaraify.ruleCount=0, externalIntel.malwareBazaar.hit=false, and externalIntel.circl.hit=false, although absent intelligence matches do not prove benignity.
- droppedChildren.inspected=9 found no confirmed malicious child, but all nine child verdicts remain unknown.
- contactedHosts=null, so no complete host-reputation cross-check is available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 15 of 17 tier-1 engines did not detect the sample
- One sandbox run produced no malicious verdict or offensive technique
- No persistence indicators were observed
- No inspected child was confirmed malicious
- Broad prevalence: 3,030 sources and 9,306 submissions since 2022
- 19/75 antivirus detections
- Two independent tier-1 detections
- Unsigned Win32 DLL
- Likely packed code with UPX1 entropy 7.99
- Static anti-analysis indicators including T1027 and T1497
- No established signer identity or history
Keep the file quarantined and endpoint protection enabled until its source and SHA-256 can be verified against an official release. If verification is unavailable, delete it and obtain a fresh copy from the publisher.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete19 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 9MITRE ATT&CK techniques
- 13spawned processes
- 0network contacts
- 39filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Used an input-capture technique that can record credentials or keystrokes.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Moderate concern: Checks which security software you have installed.
Note: Collects details about your system.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
heavy-fist.asi
1cd60d7120423b53c87d80420cc8551286da4610bd125f6244f3447f635ad489
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\System32\rundll32.exe" "C:\Users\<USER>\Desktop\readme.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
rundll32.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
WERC9F9.tmp
C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9F9.tmp
04Isolated runtime analysis - Written fileObserved
WERC9F9.tmp.dmp
C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9F9.tmp.dmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9F9.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9F9.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA38.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA38.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCAD5.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER26C6.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER2706.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER2820.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER285F.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER37B2.tmp.csv
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess3756
- \Sessions\1\BaseNamedObjects\Global\9141b65d-51f5-4743-8d0b-e936542ca277
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6044
- \Sessions\1\BaseNamedObjects\Global\AmiProviderMutex_InventoryApplicationFile
- \Sessions\1\BaseNamedObjects\Global\bb8b6301-2eb6-4703-9826-a89c42ead687
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache.
- 717fdad78e4d20f6a37c…9a3cb7Never scannednever seen before
- 663e06ca8c3019cbd6a3…2ed02cNever scannednever seen before
- f71e5c67439f395b2433…e7ff4cNever scannednever seen before
- f8bef12452511ffe5375…17bbaeNever scannednever seen before
- 57882c215b25817b5881…ea1725Never scannednever seen before
- 9007eda499fc05ba4be5…42d211Never scannednever seen before
- 821de56c8fdeb6b60972…46903fNever scannednever seen before
- c0c8a217b96cacffa0ec…5a9e11Never scannednever seen before
- c78a20ba0ea32b514083…c04bf0Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 19 / 75engines flagged
- 3,030sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
19 of 75 antivirus engines flagged the file, including AhnLab-V3 and alibabacloud.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 3,030 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 9,306 times from 3,030 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: heavy-fist.asi — 1cd60d7120423b53c87d80420cc8551286da4610bd125f6244f3447f635ad489
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\System32\rundll32.exe" "C:\Users\<USER>\Desktop\readme.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — rundll32.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: WERC9F9.tmp — C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9F9.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: WERC9F9.tmp.dmp — C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9F9.tmp.dmp
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
PE is packed (high-entropy code or known packer) AND unsigned AND at least one engine flagged it. Packing alone is common in legit software; packing + unsigned + signal is the malware-dropper pattern.
Evidencehigh-entropy code section
19 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- heavy-fist.asi
- Format
- Win32 DLL
- Code signing
- No verified publisher
- Size
- 109.0 KB
- Last analyzed
- Sep 15, 2026, 2:54 PM UTC
1cd60d7120423b53c87d80420cc8551286da4610bd125f6244f3447f635ad489Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't open it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is heavy-fist.asi safe, or is it malware?
What is heavy-fist.asi?
How many antivirus engines detected heavy-fist.asi?
What should I do if I already opened heavy-fist.asi?
How do I remove heavy-fist.asi?
What is the SHA-256 hash of heavy-fist.asi?
How up to date is this analysis of heavy-fist.asi?
Community
Member reviews and reports for this exact file hash.