Is CuteSMP-CurseForge.zip safe?
A lone DrWeb Muldrop detection is inconclusive, but observed injection, service, defense-evasion, and LSASS-related activity warrants caution with this newly seen archive.
Only 1 of 74 engines flagged the archive, and there is no independent Muldrop family consensus. However, one sandbox recorded T1055, T1543.002, T1562.001, LSASS-related activity, and direct-IP traffic whose reputation was not checked, making execution inadvisable until the source and contents are verified.
b8a2e421229c55add0…aa46b85e911e3aRecommended next actions
Before opening or extracting
Do not open or extract it until the source can be verified independently.
If you already opened or extracted 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.
Only 1 of 74 engines flagged the archive, and there is no independent Muldrop family consensus. However, one sandbox recorded T1055, T1543.002, T1562.001, LSASS-related activity, and direct-IP traffic whose reputation was not checked, making execution inadvisable until the source and contents are verified.
DrWeb alone identified Java.Muldrop.52, while 16 other tier-1 engines reported no detection, so the engine evidence does not establish a malware family. Runtime evidence is more concerning: one sandbox mapped activity to process injection, service execution, defense evasion, and possible LSASS access. The archive also contacted 162.159.36.2 directly, but no complete host-reputation result is available. None of ten inspected children was identified as malicious, although every child remains unclassified rather than confirmed benign. Because the file is newly observed and lacks signer, prevalence, similar-file, or researcher corroboration, the mixed evidence supports quarantine and further verification.
What We Detected
DrWeb was the only engine among 74 to flag the archive, identifying Java.Muldrop.52. The remaining tier-1 engines did not corroborate that family, so the detection alone is insufficient to establish Muldrop.
Threat Behavior
One completed sandbox run recorded techniques T1055, T1543.002, and T1562.001, along with a heuristic indicating access involving the LSASS process. It also observed direct contact with 162.159.36.2. Because the contacted-host reputation check was not completed or saved, that connection cannot be characterized as benign or malicious. Ten extracted children were inspected without a malicious finding, but all remain unclassified.
What To Do Now
Keep endpoint protection enabled and do not open or import the archive until its download source and expected contents are verified. If it came from a mod-distribution page, compare its SHA-256 with the publisher's official listing and rescan after additional engine coverage becomes available.
Where this verdict could be wrong4 caveats
- Sixteen of 17 reporting tier-1 engines did not flag the archive, and the Muldrop label lacks independent family consensus.
- behaviour.hasMaliciousSandboxVerdict=false, so the completed sandbox did not itself assign a malicious result.
- droppedChildren.hasMaliciousChild=false, though all 10 inspected children have unknown verdicts.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false; these absences may reflect coverage limits rather than innocence.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1 of 74 engines detected the archive
- No strong tier-1 family consensus
- No malicious sandbox verdict
- No identified malicious child among 10 inspected files
- No CIRCL, MalwareBazaar, or YARAify corroboration
- One tier-1 detection naming Java.Muldrop.52
- Observed MITRE technique T1055
- Observed MITRE technique T1543.002
- Observed MITRE technique T1562.001
- Heuristic activity involving lsass.exe
- Direct connection to 162.159.36.2 without a completed reputation check
Quarantine the archive and verify its SHA-256 against the official distribution source before use. Keep endpoint protection enabled and avoid executing or importing its contents until further corroboration is available.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete3 signature or behavior rules 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
- 10MITRE ATT&CK techniques
- 15spawned processes
- 1network contacts
- 16filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Created or modified a system service, which can keep code running.
High concern: Attempted to impair or bypass security controls.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Moderate concern: Checks which security software you have installed.
Note: Reads your Windows user-account details.
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
CuteSMP-CurseForge.zip
b8a2e421229c55add0826426ef59ea4b614494c5bc9c3ea702aa46b85e911e3a
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\cmd.exe" /c "cd ^"C:\Users\<USER>\AppData\Local\Temp^" && start /wait ^"^" ^"C:\Users\<USER>\AppData\Local\Temp\manifest.json^"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\slui.exe -Embedding
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
s0sy2ywy.fpf
C:\Users\user\AppData\Local\Temp\s0sy2ywy.fpf
04Isolated runtime analysis - Written fileObserved
manifest.json
C:\Users\user\AppData\Local\Temp\s0sy2ywy.fpf\manifest.json
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- C:\Users\user\AppData\Local\Temp\s0sy2ywy.fpf
- C:\Users\user\AppData\Local\Temp\s0sy2ywy.fpf\manifest.json
- C:\Users\user\AppData\Local\Temp\s0sy2ywy.fpf\overrides
- C:\Users\user\AppData\Local\Temp\s0sy2ywy.fpf\overrides\config
- C:\Users\user\AppData\Local\Temp\s0sy2ywy.fpf\overrides\config\iris.properties
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 5b8ce80bd59ad779b94b…8506b6Never scannednever seen before
- 3a8d57d336378c3acd12…d99b20Never scannednever seen before
- a36780099062c1414017…d047e7Never scannednever seen before
- defbefad7b40e2a8902f…394b8aNever scannednever seen before
- 3a6c9c6ae08653658ac4…7e5d93Never scannednever seen before
- 87c3d66ba72e0e034c1a…4add73Never scannednever seen before
- ee148cc9c3411abd1f2c…488964Never scannednever seen before
- 65b41aa30a824b1dc812…51d956Never scannednever seen before
- e4a22bc14751a3f8bdad…bd5d7bNever scannednever seen before
- c8e31de1848c39bcdbf0…ed434eNever 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.
- 3rule hits recorded
- 1 / 74engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
1 of 74 antivirus engines flagged the file, including DrWeb.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: CuteSMP-CurseForge.zip — b8a2e421229c55add0826426ef59ea4b614494c5bc9c3ea702aa46b85e911e3a
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\cmd.exe" /c "cd ^"C:\Users\<USER>\AppData\Local\Temp^" && start /wait ^"^" ^"C:\Users\<USER>\AppData\Local\Temp\manifest.json^"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\slui.exe -Embedding
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: s0sy2ywy.fpf — C:\Users\user\AppData\Local\Temp\s0sy2ywy.fpf
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: manifest.json — C:\Users\user\AppData\Local\Temp\s0sy2ywy.fpf\manifest.json
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
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
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Windows\system32\NOTEPAD.EXE" C:\Users\<USER>\AppData\Local\Temp\manifest.jsonSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence162.159.36.2
1 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. 1 antivirus detection make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- CuteSMP-CurseForge.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 18.4 MB
- Last analyzed
- Sep 16, 2026, 11:18 PM UTC
b8a2e421229c55add0826426ef59ea4b614494c5bc9c3ea702aa46b85e911e3aSafety & 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 or extract 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 archive 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 CuteSMP-CurseForge.zip safe, or is it malware?
What is CuteSMP-CurseForge.zip?
How many antivirus engines detected CuteSMP-CurseForge.zip?
What should I do if I already opened or extracted CuteSMP-CurseForge.zip?
How do I remove CuteSMP-CurseForge.zip?
What is the SHA-256 hash of CuteSMP-CurseForge.zip?
How up to date is this analysis of CuteSMP-CurseForge.zip?
Community
Member reviews and reports for this exact file hash.