File scan report
Verdict Safe
Is alsoft.
alsoft.ini is a benign configuration file with zero malicious detections across 61 engines and 5-year established prevalence.
Read the whole reasonShow less
Strong evidence · Widely seen for a long time, and nothing harmful found.
Good practice2 tips
We found nothing harmful in this file.
Open it only if you trust the person or website it came from.
Keep your security software and system updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 61 flagged
- Flagged 0
- No detection 61
- No result 14
- Code signing Not applicable
- Test run Completed
- First seen 5y ago
Chapter 02
Why we think so
0 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
This 31-byte INI configuration file shows no malicious indicators. All 17 major antivirus engines (BitDefender, Kaspersky, Microsoft, ESET-NOD32, Fortinet, and others) report it clean. The file has been widely distributed (4,148 submissions, 2,995 sources) since 2021 with no sandbox malicious verdicts or external-intelligence hits. Independent third-party analysis confirms no threat.
alsoft.ini is a configuration file (INI format, 31 bytes) with zero detections across 61 reporting engines, including unanimous agreement from 17 major antivirus engines. The file's 5-year prevalence history (widely seen and long established classification) with 4,148 submissions demonstrates it is an established benign commodity. Sandbox analysis detected only routine system-discovery techniques (scripting, protocol enumeration, system-info queries) — normal for configuration processing. No complete contacted-host reputation result was available. No files it created, no external-intelligence corroboration of threats. Five independent FileScan.IO analyses independently returned NO_THREAT verdicts with 100% confidence, reinforcing the safety assessment.
What We Detected
alsoft.ini is a 31-byte configuration file in INI format. The antivirus engines scanned it across 61 engines, with 17 major antivirus engines (BitDefender, Kaspersky, Microsoft, ESET-NOD32, Fortinet, Emsisoft, F-Secure, GData, Ikarus, Avira, AVG, DrWeb, Avast) all reporting it clean. Zero malicious detections were recorded.
Threat Behavior
Sandbox analysis identified three MITRE techniques common in legitimate software (T1064 scripting, T1071 application-layer protocol use, T1082 system-information discovery) — all benign patterns consistent with normal configuration file processing. No malicious sandbox verdicts, no a control server contact, no dropped files, no persistence indicators were observed. The file has been widely distributed (4,148 submissions from 2,995 sources) since April 2021 with no escalation in threat reports.
What To Do Now
No action required. This file is safe to use. It is a standard configuration file with an established 5-year clean history and unanimous agreement from leading antivirus vendors.
Where this verdict could be wrong3 caveats
- INI files can be configuration vectors for malware if paired with a malicious loader — however, this file's 5-year prevalence history (widely seen and long established), unanimous major clean consensus, and zero sandbox malicious verdicts rule out active exploitation.
- The file was analyzed in a sandbox environment (sandboxCount=1) but returned no malicious verdict — if it were a malicious config, we would expect at least one sandbox engine to flag suspicious behaviour or a control server contact.
- No signer history available (unsigned) — but unsigned config files are normal; the risk would only elevate if detections or behaviour were present, which they are not.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 17 major antivirus engines report clean (BitDefender, Kaspersky, Microsoft, ESET-NOD32, Fortinet, Emsisoft, F-Secure, GData, Ikarus, Avira, AVG, DrWeb, Avast)
- 4,148 submissions across 2,995 sources since 2021 — widely seen and long established prevalence classification
- Zero malicious sandbox verdicts; no a control server contact or files it created
- 5 independent FileScan.IO analyses all returned NO_THREAT with 100/100 confidence
- INI configuration file format (non-executable, inherently low-risk)
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 3sandbox rule tags
- 3spawned processes
- 0network contacts
- 0filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
3MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1064
- T1071· Application protocol
- T1082· System recon
Observed activity
Processes started
3Programs the file ran, with their command lines.
wscript.exe"C:\Windows\system32\wscript.exe" "C:\Users\<USER>\AppData\Local\Temp\script.js"wmiprvse.exeC:\Windows\system32\wbem\wmiprvse.exe -secured -Embeddingwscript.exeC:\Windows\System32\wscript.exe C:\Windows\System32\WScript.exe "C:\Users\user\Desktop\sample.js"
Sandbox background — not the file
3The analysis machine's own processes and connections, recorded in every run.
- VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\system32\svchost.exe -k DcomLaunch -p - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalService -p -s LicenseManager
Chapter 04
Technical details
None of the 61 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Jun 10, 2026, 1:54 PM UTC
- SHA-256
37b67ff73aa4fdd271c32e9652946e2557b0fc94ff460de6fc7983d00ae21f5d- SHA-1
c616cb514944d07c6c7b6fca1b08286538cff2f2- MD5
c0a92d39626eab678620c85e8eff1730
About this file
alsoft.ini is an INI file of 31 B.
- Type and size
- INI · 31 B
- Signer
- Not applicable
- First seen
- Apr 5, 2021On VirusTotal.
- Submitted by
- 2,995 distinct sources
First scanned
Antivirus consensus
0 of 61 engines flagged this file
14 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines0flagged
- Tier-232 engines0flagged
- Low-trust11 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaNo result
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXNo result
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- CynetClean
- DeepInstinctNo result
- DrWebClean
- ElasticNo result
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoNo result
- PandaClean
- RisingClean
- SangforClean
- SentinelOneNo result
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrapmineNo result
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootNo result
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
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.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is alsoft.ini safe?
What is alsoft.ini?
How many antivirus engines detected alsoft.ini?
What is the SHA-256 hash of alsoft.ini?
Is it safe to open alsoft.ini?
How up to date is this analysis of alsoft.ini?
Community
Member reviews and reports for this exact file hash.