Is Rockey4ND_X64.dll safe?
One tier-1 Convagent detection and unresolved direct-IP traffic warrant caution, although most engines and the completed sandbox provide no corroborating malware verdict.
Four of 75 engines flagged this unsigned DLL, with Kaspersky naming Convagent and Rising offering a matching family label. However, tier-1 consensus is absent, one sandbox produced no malware verdict or offensive-only techniques, and the contacted IP was not reputation-checked, leaving materially mixed evidence.
ef476d7bee99c375eb…23455bf9cdd00bRecommended next actions
Before using
Do not use it until the source and publisher can be verified independently.
If you already used it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Reinstall the parent software from the developer's official site instead of replacing this component by itself.
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.
Four of 75 engines flagged this unsigned DLL, with Kaspersky naming Convagent and Rising offering a matching family label. However, tier-1 consensus is absent, one sandbox produced no malware verdict or offensive-only techniques, and the contacted IP was not reputation-checked, leaving materially mixed evidence.
Kaspersky identified the DLL as a Convagent backdoor, but it is the sole tier-1 malicious vote among 17 tier-1 engines. Three additional detections exist, although two are generic and only Rising repeats the Convagent family. One completed sandbox recorded six ambient techniques and no malware verdict, persistence, dropped hashes, or malware-exclusive techniques. It did contact 162.159.36.2 directly, but no complete host-reputation result is available because the contacted-host check was not saved. The unsigned status removes a useful publisher assurance, while the unpacked PE structure and absence of external-intelligence hits reduce corroboration. A single safe imphash match without signer co-match is too weak to resolve these conflicting signals.
What We Detected
Four of 75 antivirus engines flagged Rockey4ND_X64.dll. Kaspersky reported VHO:Backdoor.Win32.Convagent.gen, Rising reported Backdoor.Convagent, and Cynet and McAfeeD supplied generic detections. Kaspersky is the only tier-1 engine detecting it, so there is no strong independent tier-1 family consensus.
Threat Behavior
One completed sandbox run recorded six ambient MITRE techniques, including T1027, T1071, and T1497, but no offensive-only techniques, persistence indicators, dropped hashes, or malware verdict. The DLL contacted 162.159.36.2 directly. The host-reputation cross-check was not completed or saved, so that no complete contacted-host reputation result was available or malicious.
Additional Context
The DLL is unsigned even though signing is applicable, and no publisher history is available. Static PE analysis found no packer, no likely packing, and no high-entropy code. CIRCL, MalwareBazaar, and YARAify supplied no corroborating hit. One prior safe sample shares the imphash, but it has no signer co-match and therefore may only share a common build framework.
What To Do Now
Do not load or register this DLL on a production system until its source and expected vendor can be verified. Keep endpoint protection enabled, quarantine the file if it arrived unexpectedly, and obtain a fresh copy from the software vendor's official distribution channel.
Where this verdict could be wrong4 caveats
- Kaspersky, a tier-1 engine, identified Backdoor.Win32.Convagent, and Rising independently used the same Convagent family name.
- The sandbox contacted 162.159.36.2 directly; because contactedHosts=null, no complete host-reputation result is available.
- The DLL is unsigned despite code signing being applicable, so no publisher identity or clean signer history can be established.
- A similar imphash received a prior safe decision, but matchKind=imphash with signerCoMatch=false is weak because unrelated binaries can share build frameworks.
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 4/75 engines reported a malicious result
- engines.tier1FamilyConsensus.strong=false
- behaviour.hasMaliciousSandboxVerdict=false in one completed run
- behaviour.offensiveCount=0 and no persistence indicators were recorded
- peAnalysis.likelyPacked=false and peAnalysis.highEntropyCode=false
- Kaspersky tier-1 detection names Backdoor.Win32.Convagent
- Rising independently repeats the Convagent family label
- Unsigned Win32 DLL with no established signer history
- Direct-IP contact to 162.159.36.2 has no saved host-reputation result
- File tags include detect-debug-environment and long-sleeps
Keep endpoint protection enabled and avoid loading this DLL unless its origin and expected vendor are independently verified. Prefer a replacement downloaded from the vendor's official channel.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
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
- 6MITRE ATT&CK techniques
- 7spawned processes
- 1network contacts
- 1filesystem & mutex artifacts
What this file does
Observed actions and their security significance
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
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.
Note: Loads extra code modules while running.
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
Rockey4ND_X64.dll
ef476d7bee99c375eb77b04657200b441bedd20c5aa6c7310923455bf9cdd00b
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\attachment.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\library.dll"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Connect
\Device\ConDrv\\Connect
04Isolated runtime analysis
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
05Isolated runtime analysis
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.
- 162.159.36.2
- \Device\ConDrv\\Connect
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
- 4 / 75engines flagged
- 4sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
4 of 75 antivirus engines flagged the file, including Cynet and Kaspersky.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 4 times from 4 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: Rockey4ND_X64.dll — ef476d7bee99c375eb77b04657200b441bedd20c5aa6c7310923455bf9cdd00b
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\attachment.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\library.dll"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: Connect — \Device\ConDrv\\Connect
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
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
Low-severity pattern matches — worth noting but not on their own cause for alarm.
The 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
4 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Rockey4ND_X64.dll
- Format
- Win32 DLL
- Code signing
- No verified publisher
- Size
- 90.5 KB
- Last analyzed
- Sep 8, 2026, 9:11 AM UTC
ef476d7bee99c375eb77b04657200b441bedd20c5aa6c7310923455bf9cdd00bSafety & 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 use 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
Do not delete or replace the component manually. Quarantine it with your antivirus or repair the parent software from its official source. Reinstall the parent software from the developer's official site instead of replacing this component by itself.
- 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 Rockey4ND_X64.dll safe, or is it malware?
What is Rockey4ND_X64.dll?
How many antivirus engines detected Rockey4ND_X64.dll?
What should I do if I already used Rockey4ND_X64.dll?
How do I remove Rockey4ND_X64.dll?
What is the SHA-256 hash of Rockey4ND_X64.dll?
How up to date is this analysis of Rockey4ND_X64.dll?
Community
Member reviews and reports for this exact file hash.