Is a4a414.msi safe?
This legitimate remote administration tool is being repurposed by threat actors as a component in ransomware deployment campaigns, as evidenced by its presence in known malicious staging infrastructure.
While this file is a signed installer for legitimate software, it has been identified as a tool used by the GOLD SALEM threat group for ransomware operations. The observed behavior, including credential dumping and process injection, confirms its malicious application in this context.
85844ae7394f2cf907…985adf4f53320eRecommended next actions
Before installing
Do not install it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already installed 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.
While this file is a signed installer for legitimate software, it has been identified as a tool used by the GOLD SALEM threat group for ransomware operations. The observed behavior, including credential dumping and process injection, confirms its malicious application in this context.
Our analysis confirms that this file is a legitimate Radmin Server installer. However, security research identifies this specific sample as part of a malicious tool-staging server used by the GOLD SALEM threat group. The sandbox behavior, including LSASS access and process injection, aligns with the group's known tradecraft for disabling security and deploying ransomware. Because the file is being actively used to facilitate malicious activity, it is classified as malicious despite its legitimate origin.
What We Detected
The file is a signed installer for Radmin Server 3.5.2. While the binary itself is a legitimate remote administration tool, it has been identified in multiple security reports as a component staged by the GOLD SALEM threat group for use in ransomware attacks.
Threat Behavior
Our sandbox analysis observed behavior inconsistent with standard administrative use, including attempts to access the LSASS process (credential dumping) and process injection (MITRE T1055). These techniques are characteristic of the group's efforts to disable security products and escalate privileges within compromised environments.
What To Do Now
If this file was not intentionally deployed by your IT department for remote administration, it should be removed immediately. If you are using Radmin for legitimate purposes, ensure that it is deployed from an official, trusted source and that access is strictly restricted to authorized personnel only.
Where this verdict could be wrong2 caveats
- The file is a legitimate, signed installer for Radmin Server, which is widely used for valid remote administration purposes.
- The majority of antivirus engines (73/74) did not flag the file as malicious, suggesting that the malicious activity is context-dependent rather than inherent to the binary itself.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Signed by legitimate publisher Famatech Corp.
- Commonly used remote administration software
- Known association with GOLD SALEM ransomware operations
- Observed credential dumping behavior (LSASS access)
- Observed process injection techniques
- Used as a staging tool for malicious infrastructure
Remove this file immediately if it was not authorized by your organization. If
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
Partial7 of 16 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete4 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
- 26MITRE ATT&CK techniques
- 15spawned processes
- 17network contacts
- 40filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Created or modified a scheduled task, which can provide persistence.
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used removable-media replication behaviour that can spread files between devices.
High concern: Created or modified a system service, which can keep code running.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
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
a4a414.msi
85844ae7394f2cf907b6378b415e77f7e29069c7e791598cf0985adf4f53320e
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\setup.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
ngen.log
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
04Isolated runtime analysis - Written fileObserved
~DF0BF5A31CBEDC3844.TMP
C:\Windows\Temp\~DF0BF5A31CBEDC3844.TMP
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
8.250.15.254
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
23.43.75.27
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.
- 8.250.15.254
- 23.43.75.27
- 8.8.8.8
- 23.54.127.164
- 23.13.144.239
- 172.66.2.5
- 92.223.96.6
- 199.232.214.172
- 23.207.202.23
- http://s1.symcb.com/pca3-g5.crl
- http://sv.symcb.com/sv.crl
- http://sf.symcd.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBTSqZMG5M8TA9rdzkbCnNwuMAd5VgQUz5mp6nsm9EvJjo%2FX8AUm7%2BPSp50CEFEDDjs4nB8tdp6g5l%2BaE0I%3D
- http://sf.symcb.com/sf.crl
- http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/disallowedcertstl.cab?4de32416528c2b24
- http://s2.symcb.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBS56bKHAoUD%2BOyl%2B0LhPg9JxyQm4gQUf9Nlp8Ld7LvwMAnzQzn6Aq8zMTMCED141%2Fl2SWCyYX308B7Khio%3D
- RServer3
- raddrvv3
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
- C:\Windows\Temp\~DF0BF5A31CBEDC3844.TMP
- C:\Windows\Temp\~DF346FC566E4EB9932.TMP
- C:\Windows\Temp\~DFD7FC132E6821B800.TMP
- C:\Windows\Temp\~DFD3B5DABAE1382FFB.TMP
- C:\Config.Msi\CMPEC05.tmp
- C:\Config.Msi
- C:\Windows\Installer\ded9.msi
- C:\Config.Msi\CMP4800.tmp
- C:\Config.Msi\ded8.rbs
- Global\_MSIExecute
- \Sessions\1\BaseNamedObjects\Global\_MSIExecute
- \Sessions\1\BaseNamedObjects\Global\RasPbFile
- \BaseNamedObjects\Local\SM0:4336:168:WilStaging_02
- \BaseNamedObjects\DBWinMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 3d7486da3ee69c76679c…a63028Never scannednever seen before
- e99126606ac09dff681d…753323Never scannednever seen before
- 706c5b1053c72f17dae0…1262a6Never scannednever seen before
- 565175e156b9f0dd5771…263f0aNever scannednever seen before
- 639b98493874c75bc3c4…3385b7Never scannednever seen before
- 3a981fa959778f7b4781…d907f9Never scannednever seen before
- 943b1ed865fcab8264d0…020988Never scannednever seen before
- e02e59e4af1e5ce3c475…f7450fNever scannednever seen before
- b1442a756211a2a6e6fc…585fb6Never scannednever seen before
- 0514bb5d11658cfbd295…3bdcb5Never 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.
- 4rule hits recorded
- 1 / 74engines flagged
- 460sources 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 AhnLab-V3.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 460 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: a4a414.msi — 85844ae7394f2cf907b6378b415e77f7e29069c7e791598cf0985adf4f53320e
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\setup.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ngen.log — C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: ~DF0BF5A31CBEDC3844.TMP — C:\Windows\Temp\~DF0BF5A31CBEDC3844.TMP
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 8.250.15.254 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 23.43.75.27 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: hacktool
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.
Sandbox flagged persistence indicators (registry Run keys / services / scheduled tasks).
EvidenceRServer3 · raddrvv3The 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.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox 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.
Evidence8.250.15.254 · 23.43.75.27 · 23.54.127.164
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
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
- a4a414.msi
- Format
- Windows Installer
- Code signing
- Signature valid: Famatech Corp.
- Size
- 4.3 MB
- Last analyzed
- Jul 26, 2026, 1:25 AM UTC
85844ae7394f2cf907b6378b415e77f7e29069c7e791598cf0985adf4f53320eSafety & 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 install this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already installed 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
Download a fresh installer 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 a4a414.msi a virus?
What is a4a414.msi?
How many antivirus engines detected a4a414.msi?
What should I do if I already installed a4a414.msi?
How do I remove a4a414.msi?
What kind of malware is a4a414.msi?
Is a4a414.msi digitally signed?
What is the SHA-256 hash of a4a414.msi?
How up to date is this analysis of a4a414.msi?
Community
Member reviews and reports for this exact file hash.