Is exportrsa.exe safe?
Hacktool for exporting non-exportable RSA private keys, confirmed by YARA rule HKTL_ExportRSA_Feb22_1, process injection (T1055), and evasion tags.
This unsigned executable matches a known hacktool via community YARA rule for ExportRSA, exhibiting process injection and direct IP connections typical of offensive tools. Tier-1 engines like TrendMicro detect it as Trojan.URSU. Despite majority clean detections, behavioral heuristics and anti-analysis tags confirm malicious intent as a hacktool.
99e23a621c88854578…7bcf6aa3b0a97bRecommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
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.
This unsigned executable matches a known hacktool via community YARA rule for ExportRSA, exhibiting process injection and direct IP connections typical of offensive tools. Tier-1 engines like TrendMicro detect it as Trojan.URSU. Despite majority clean detections, behavioral heuristics and anti-analysis tags confirm malicious intent as a hacktool.
Two tier-1 engines from TrendMicro agree on URSU family, paired with high-severity process injection heuristic and direct-IP C2 pattern. Community annotation explicitly identifies it as an open-source hacktool for private key export, aligning with filename 'exportrsa.exe' and evasion behaviors like debug detection and long sleeps. No signing or trusted history, common but zero-reputation prevalence supports non-benign status. Clean sandbox and children do not outweigh converging hacktool signals.
What We Detected
Unsigned Win32 EXE with imphash 34d08a421333a7633f63a02a350bd27b, flagged by TrendMicro as Trojan.Win32.URSU.AE. Community YARA hit: HKTL_ExportRSA_Feb22_1 (hacktool for non-exportable key export).
Threat Behavior
Process injection (T1055), direct connections to 20 IPs (no DNS), anti-analysis (detect-debug-environment, long-sleeps, direct-cpu-clock-access). Writes to \Device\ConDrv.
What To Do Now
Quarantine immediately. Matches known hacktool; scan system for key export activity.
Where this verdict could be wrong4 caveats
- tier1ReportedClean=15/17 — majority of high-trust engines undetected.
- behaviour.hasMaliciousSandboxVerdict=false; no consensus in 1 sandbox.
- droppedChildren.hasMaliciousChild=false; child SHA256 2a3a3e99... unknown verdict.
- prevalence.classification=common_old (159 submissions) but reputation=0 may indicate niche tool.
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/17 tier1 clean
- No malicious sandbox verdict
- No malicious dropped children
- Common_old prevalence (159 subs)
- Hacktool: Exports non-exportable private keys
- Process injection (MITRE T1055)
- Direct IP C2 (20 IPs, no DNS)
- Evasion: detect-debug-environment, long-sleeps
- Tier-1 detections: TrendMicro URSU
- Unsigned, zero reputation
Treat as confirmed hacktool and remove. Monitor for private key tampering or injected processes; full system scan recommended.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete2 signature or behavior rules matched.
External intel
Not runNo independent reference checks are recorded.
No timestamp recorded
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 6MITRE ATT&CK techniques
- 10spawned processes
- 20network contacts
- 17filesystem & 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.
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: Collects details about your system.
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.
Threat context
How hacktools are abused
This is a hacking or cracking tool — the kind used to bypass software licences, generate fake keys, or attack other systems. Even when the tool 'works', these downloads very often carry hidden malware.
Bottom line:Running one means trusting an anonymous author with full access to your PC — rarely worth the risk.
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
exportrsa.exe
99e23a621c888545780f610f418d6dc63f1decc4a0e8838ccf7bcf6aa3b0a97b
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\99e23a621c888545780f610f418d6dc63f1decc4a0e8838ccf7bcf6aa3b0a97b.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
ConDrv
\Device\ConDrv
04Isolated runtime analysis - Written fileObserved
Connect
\Device\ConDrv\\Connect
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
204.79.197.203
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
23.216.147.64
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 204.79.197.203
- 23.216.147.64
- 52.251.79.25
- 20.99.132.105
- 20.99.184.37
- 23.216.147.76
- 20.99.133.109
- 192.229.211.108
- 131.253.33.203
- 20.99.186.246
- \Device\ConDrv
- \Device\ConDrv\\Connect
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C3D.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C4F.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C50.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C4.tmp.WERInternalMetadata.xml
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- 2a3a3e99cf772c20d567…28e263Never 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.
- 2rule hits recorded
- 4 / 76engines flagged
- 150sources 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
4 of 76 antivirus engines flagged the file, including CAT-QuickHeal and TrellixENS.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 150 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: exportrsa.exe — 99e23a621c888545780f610f418d6dc63f1decc4a0e8838ccf7bcf6aa3b0a97b
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\99e23a621c888545780f610f418d6dc63f1decc4a0e8838ccf7bcf6aa3b0a97b.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ConDrv — \Device\ConDrv
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Connect — \Device\ConDrv\\Connect
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 204.79.197.203 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 23.216.147.64 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: hacktool
This legacy report does not record whether the independent reference checks completed.
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.
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
Evidence"C:\Users\<USER>\AppData\Local\Temp\executable.exe"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.
Evidence204.79.197.203 · 23.216.147.64 · 52.251.79.25
4 of 76 engines flagged this file
View all 76 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
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
- exportrsa.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 17.5 KB
- Last analyzed
- May 9, 2026, 7:51 AM UTC
99e23a621c888545780f610f418d6dc63f1decc4a0e8838ccf7bcf6aa3b0a97bSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
If you typed any passwords while it was open, change them from a device you trust.
- Recovery step 04
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is exportrsa.exe malware?
What is exportrsa.exe?
How many antivirus engines detected exportrsa.exe?
I already downloaded and ran exportrsa.exe — what should I do?
How do I remove exportrsa.exe?
What kind of malware is exportrsa.exe?
What is the SHA-256 hash of exportrsa.exe?
How up to date is this analysis of exportrsa.exe?
Community
Member reviews and reports for this exact file hash.