Is XP_Search_Assistant_Rewritten_Setup_1.2.exe safe?
Only Zillya flagged this unsigned installer, while 17 tier-1 engines and one completed sandbox run provided no corroborating malware evidence.
The Viking label comes from only 1 of 75 engines, with no tier-1 detections or family consensus. One sandbox run produced no malicious verdict or malware-specific techniques, but the unsigned status, unresolved direct-IP contact, and unknown child-file verdicts justify retaining some caution.
11c4738faa8259ae85…d7898f117d3994Recommended next actions
Before installing
Install it only when it came from the developer's official site or an official app store.
If you already installed it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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 Viking label comes from only 1 of 75 engines, with no tier-1 detections or family consensus. One sandbox run produced no malicious verdict or malware-specific techniques, but the unsigned status, unresolved direct-IP contact, and unknown child-file verdicts justify retaining some caution.
Zillya alone reported the Viking family among 75 engines, while all 17 reporting tier-1 engines remained silent. The completed sandbox run had no malicious verdict and no offensive techniques, which does not support worm activity. Six dropped files were inspected without a malicious child finding, although their individual verdicts remain unknown. The direct contact to 162.159.36.2 is a mild concern because no complete host-reputation result is available. The absent signature reduces publisher assurance, but it does not outweigh the broad lack of corroboration.
What We Detected
Zillya was the only engine among 75 to report the file, naming Worm.Viking.Win32.22518. None of the 17 reporting tier-1 engines detected it, and there was no tier-1 family consensus. The executable is unsigned and has no established signer history.
Threat Behavior
One completed sandbox run produced no malicious verdict and no malware-specific offensive techniques. The installer wrote temporary setup components and produced six child hashes; none was identified as malicious, although all six child verdicts remain unknown. It also contacted 162.159.36.2 directly, but the host-reputation cross-check was not completed or saved, so that connection cannot be characterized as benign or malicious.
What To Do Now
Obtain the installer from the project's official release channel and verify its SHA-256 value before running it. Keep endpoint protection enabled, and avoid execution if the source or expected hash cannot be confirmed.
Where this verdict could be wrong4 caveats
- Zillya identified Worm.Viking.Win32.22518, but no second engine or tier-1 engine corroborated that family.
- The executable is unsigned: signing.signed=false and signing.signerStats.found=false, so publisher identity and historical signer reputation cannot support it.
- The sandbox contacted 162.159.36.2 directly; because contactedHosts=null, no complete reputation assessment is available.
- All six inspected dropped children have unknown verdicts despite droppedChildren.hasMaliciousChild=false, limiting confidence in their safety.
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/75 engines reported malware
- engines.tier1Malicious=0 and 17 reporting tier-1 engines were clean
- behaviour.hasMaliciousSandboxVerdict=false with behaviour.offensiveCount=0
- droppedChildren.hasMaliciousChild=false
- externalIntel.yaraify.ruleCount=0 and externalIntel.circl.hit=false
- signing.signed=false; publisher identity is not authenticated
- Zillya reported Worm.Viking.Win32.22518
- Direct-IP contact to 162.159.36.2 has no completed host-reputation result
- Six dropped children have unknown individual verdicts
Use only a copy obtained from the official project channel and compare SHA-256 11c4738faa8259ae85d08fa06c326aef9b5a7fa6ed6a09fa5fd7898f117d3994 before execution. Keep endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 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
- 17MITRE ATT&CK techniques
- 2spawned processes
- 1network contacts
- 19filesystem & mutex artifacts
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
XP_Search_Assistant_Rewritten_Setup_1.2.exe
11c4738faa8259ae85d08fa06c326aef9b5a7fa6ed6a09fa5fd7898f117d3994
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\XP_Search_Assistant_Rewritten_Setup_1.2.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\XP_Search_Assistant_Rewritten_Setup_1.2.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
nsiB97D.tmp
C:\Users\<USER>\AppData\Local\Temp\nsiB97D.tmp
04Isolated runtime analysis - Written fileObserved
LangDLL.dll
C:\Users\<USER>\AppData\Local\Temp\nsyB98E.tmp\LangDLL.dll
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\nsiB97D.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsyB98E.tmp\LangDLL.dll
- C:\Users\<USER>\AppData\Local\Temp\nsyB98E.tmp\modern-header.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsyB98E.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsyB98E.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Temp\nso6A34.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsp6A85.tmp
- C:\Users\user\AppData\Local\Temp\nse4BC0.tmp
- C:\Users\user\AppData\Local\Temp\nsv5B91.tmp
Files this sample writes at runtime
This file drops 6 children at runtime. None are currently flagged malicious in our cache.
- 4cd17f660560934a001f…d13061Never scannednever seen before
- fd26ef21d72797fedecd…e197b6Never scannednever seen before
- bb6df93369b498eaa638…f5e0f1Never scannednever seen before
- 166cac68ea5b8518a647…2980e4Never scannednever seen before
- bedcdb63f027107c471f…4f768bNever scannednever seen before
- 3ad2dc318056d0a2024a…056cf2Never 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
- 1 / 75engines flagged
- 19sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 of 75 antivirus engines flagged the file, including Zillya.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 22 times from 19 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: XP_Search_Assistant_Rewritten_Setup_1.2.exe — 11c4738faa8259ae85d08fa06c326aef9b5a7fa6ed6a09fa5fd7898f117d3994
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\XP_Search_Assistant_Rewritten_Setup_1.2.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\user\Desktop\XP_Search_Assistant_Rewritten_Setup_1.2.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: nsiB97D.tmp — C:\Users\<USER>\AppData\Local\Temp\nsiB97D.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: LangDLL.dll — C:\Users\<USER>\AppData\Local\Temp\nsyB98E.tmp\LangDLL.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
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
1 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
- XP_Search_Assistant_Rewritten_Setup_1.2.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 14.1 MB
- Last analyzed
- Sep 14, 2026, 3:19 AM UTC
11c4738faa8259ae85d08fa06c326aef9b5a7fa6ed6a09fa5fd7898f117d3994Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Install it only when it came from the developer's official site or an official app store.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is XP_Search_Assistant_Rewritten_Setup_1.2.exe safe?
What is XP_Search_Assistant_Rewritten_Setup_1.2.exe?
How many antivirus engines detected XP_Search_Assistant_Rewritten_Setup_1.2.exe?
What is the SHA-256 hash of XP_Search_Assistant_Rewritten_Setup_1.2.exe?
Is it safe to install XP_Search_Assistant_Rewritten_Setup_1.2.exe?
How up to date is this analysis of XP_Search_Assistant_Rewritten_Setup_1.2.exe?
Community
Member reviews and reports for this exact file hash.