File scan report
Verdict Suspicious
Is SDF-
No engines detected this new batch script, but its PowerShell bypass, temporary C# compilation, and offensive technique mappings warrant caution pending provenance verification.
Read the whole reasonShow less
Why Suspicious? The file was first observed on Oct 11, 2026 and has only one known submission, so it has no established distribution history.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 60 flagged
- Flagged 0
- No detection 60
- No result 15
- Code signing Not applicable
- Test run Completed
- First seen 15d ago
Chapter 02
Why we think so
4 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 60 antivirus engines that checked it flagged the file, and the observed destinations produced no hostile reputation matches. However, this script launched PowerShell with an execution-policy bypass, compiled temporary C# code, and received mappings for injection, data destruction, and security-control impairment, so it should not be run without confirming its source and purpose.
The antivirus evidence is favorable: none of the 60 antivirus engines that checked it flagged the file, including 17 major antivirus engines that reported no detection. One completed sandbox recorded PowerShell with an execution-policy bypass and temporary C# compilation, alongside T1055, T1485, and mappings. Those mappings are concerning, but the evidence does not name an injection target, and the sandbox issued no malicious verdict. Reputation checks covered all 33 distinct observed domains and IPs without finding a malicious or suspicious destination. Because the script is lacks established provenance, and produced ten children with no saved classifications, the behavioral concerns remain unresolved despite the strong counter-signals.
What We Detected
None of the 60 antivirus engines that checked it flagged the batch/PowerShell script. This includes 17 major antivirus engines that reported no detection, and no engine supplied a malware-family label.
Threat Behavior
The completed sandbox observed the script extracting and launching temporary PowerShell with an execution-policy bypass, then invoking the C# compiler on temporary source. These mappings describe potentially offensive capabilities, but no injected target was recorded and the sandbox did not issue a malicious verdict. Reputation coverage included all 33 distinct observed domains and IPs, with no malicious or suspicious cache matches.
What To Do Now
Do not run the script solely because antivirus detections are absent. Verify its origin, review the batch and embedded PowerShell content, and test only in an isolated environment if its business purpose is established; keep security software enabled throughout.
Where this verdict could be wrong3 caveats
- No antivirus engine detected the script, including the 17 major antivirus engines that reported a result.
- The completed sandbox did not issue a malicious verdict, and no observed destination matched the malicious or suspicious host cache.
- The mapping names no injection target, and the recorded injected-process list is empty.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 60 antivirus engines that checked it flagged the file.
- Seventeen major antivirus engines reported no detection.
- The completed sandbox produced no malicious verdict.
- All 33 distinct observed domains and IPs were covered by the host-reputation check, with no malicious or suspicious matches.
- No persistence indicators or registry modifications were recorded.
- The file was first observed on Oct 11, 2026 and has only one known submission, so it has no established distribution history.
- It launched PowerShell with an execution-policy bypass and wrote executable script content into a temporary directory.
- It invoked the C# compiler to build temporary code during execution.
- The test run mapped possible process injection, data destruction, and security-control impairment techniques.
6 sources checked · all complete. 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- 25sandbox rule tags
- 14spawned processes
- 28network contacts
- 27filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Downloaded a file during the test run.
Moderate concern: Checked whether it was running on a test computer.
Moderate concern: Hid files or windows on the test computer.
Note: Read the user name of the test computer.
Note: Listed the programs running on the test computer.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
SDF-43.bat
b1b19c394520bdfe1119058bc7908ff49267c36eebad8d8297e81d3ec9e713a1
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
identity_helper.exe
"C:\Program Files (x86)\Microsoft\Edge\Application\122.0.2365.92\identity_helper.exe" --type=utility --utility-sub-type=winrt_app_id.mojom.WinrtAppIdService --lang=en-US --service-sandbox-type=none --no-appcompat-clear --mojo-platform-channel-handle=6392 --field-trial-handle=2244,i,4379653910079685356,9276958589501600008,262144 --variations-seed-version /prefetch:8
Test run - Evidence 3 of 7: ProcessSeen in the test run
cmd.exe
"C:\Windows\system32\cmd.exe" /c start /wait "" "C:\Users\<USER>\Desktop\SDF-43.bat"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
warning_27931.ps1
C:\Users\<USER>\AppData\Local\Temp\warning_27931.ps1
Test run - Evidence 5 of 7: Written fileSeen in the test run
yhf2hucf.tmp
C:\Users\<USER>\AppData\Local\Temp\yhf2hucf.tmp
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostWorked out from other results
www.googleadservices.com
Older reputation report (safe), not counted as current evidence.
Contacted-host cross-check - Evidence 7 of 7: Contacted hostWorked out from other results
www.gstatic.com
Older reputation report (safe), not counted as current evidence.
Contacted-host cross-check - +1 more recorded observation
7 facts from the test run. See the full activity list.
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
25MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1027.004· Obfuscated code
- T1033· Reads user info
- T1047
- T1055· Process injection
- T1057· Lists programs
- T1059· Runs commands
- T1059.001· Runs commands
- T1064
- T1070· Covers its tracks
- T1071· Application protocol
- T1074
- T1082· System recon
- T1105· Network file transfer
- T1106
- T1129· Loads modules
- T1202
- T1485
- T1497· Sandbox evasion
- T1518· Checks your AV
- T1562· Disables security
- T1562.001· Disables security
- T1564· Hides artifacts
- T1573
- T1574· Execution hijack
Observed activity
Processes started
14Programs the file ran, with their command lines.
identity_helper.exe"C:\Program Files (x86)\Microsoft\Edge\Application\122.0.2365.92\identity_helper.exe" --type=utility --utility-sub-type=winrt_app_id.mojom.WinrtAppIdService --lang=en-US --service-sandbox-type=none --no-appcompat-clear --mojo-platform-channel-handle=6392 --field-trial-handle=2244,i,4379653910079685356,9276958589501600008,262144 --variations-seed-version /prefetch:8cmd.exe"C:\Windows\system32\cmd.exe" /c start /wait "" "C:\Users\<USER>\Desktop\SDF-43.bat"cmd.exeC:\Windows\system32\cmd.exe /K "C:\Users\<USER>\Desktop\SDF-43.bat"cmd.exeC:\Windows\system32\cmd.exe /c findstr /n /c:"###POWERSHELL###" "C:\Users\<USER>\Desktop\SDF-43.bat"findstrfindstr /n /c:"###POWERSHELL###" "C:\Users\<USER>\Desktop\SDF-43.bat"moremore +14 "C:\Users\<USER>\Desktop\SDF-43.bat"
Show all 14 entries for processes started
powershell.exepowershell.exe -NoProfile -ExecutionPolicy Bypass -STA -File "C:\Users\<USER>\AppData\Local\Temp\warning_27931.ps1" "C:\Users\<USER>\Desktop\"csc.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\csc.exe" /noconfig /fullpaths @"C:\Users\<USER>\AppData\Local\Temp\yhf2hucf.cmdline"cvtres.exeC:\Windows\Microsoft.NET\Framework\v4.0.30319\cvtres.exe /NOLOGO /READONLY /MACHINE:IX86 "/OUT:C:\Users\<USER>\AppData\Local\Temp\RES2E6D.tmp" "c:\Users\<USER>\AppData\Local\Temp\CSCB068D3B78254A57958749EBEEBD3ED7.TMP"csc.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\csc.exe" /noconfig /fullpaths @"C:\Users\<USER>\AppData\Local\Temp\nom20ol3.cmdline"cvtres.exeC:\Windows\Microsoft.NET\Framework\v4.0.30319\cvtres.exe /NOLOGO /READONLY /MACHINE:IX86 "/OUT:C:\Users\<USER>\AppData\Local\Temp\RES5FDE.tmp" "c:\Users\<USER>\AppData\Local\Temp\CSC41C7289AA55445E6BE3A145487CB6B51.TMP"msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --new-window --window-size=800,500 https://www.google.com/search?q=How%20to%20remove%20viruscmd.exeC:\Windows\System32\cmd.exe C:\Windows\system32\cmd.exe /c ""C:\Users\user\Desktop\SDF-43.bat" "cmd.exeC:\Windows\System32\cmd.exe C:\Windows\system32\cmd.exe /c findstr /n /c:"###POWERSHELL###" "C:\Users\user\Desktop\SDF-43.bat"
Network contacts
2828 hosts, listed as 15 domains, 13 addresses. Links show the host and path only.
- Domain
www.googleadservices.com - Domain
www.gstatic.com - Domain
encrypted-tbn0.gstatic.com - Domain
xpaywalletcdn.azureedge.net - Domain
play.google.com - Domain
ep1.adtrafficquality.google
Show all 28 entries for network contacts
- Domain
www.youtube.com - Domain
ep2.adtrafficquality.google - Domain
pagead2.googlesyndication.com - Domain
i.ytimg.com - Domain
googleads.g.doubleclick.net - Domain
static.doubleclick.net - Domain
www.googletagmanager.com - Domain
fonts.gstatic.com - Domain
jnn-pa.googleapis.com - IP address
150.171.110.179 - IP address
150.171.73.13 - IP address
142.251.187.94 - IP address
173.194.201.157 - IP address
172.253.58.139 - IP address
173.194.201.113 - IP address
74.125.127.155 - IP address
142.251.154.4 - IP address
108.177.9.132 - IP address
142.251.150.4 - IP address
173.194.116.119 - IP address
192.178.237.148 - IP address
74.125.27.156
Files
27Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\warning_27931.ps1 - Written
C:\Users\<USER>\AppData\Local\Temp\yhf2hucf.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\yhf2hucf.0.cs - Written
C:\Users\<USER>\AppData\Local\Temp\yhf2hucf.dll - Written
C:\Users\<USER>\AppData\Local\Temp\yhf2hucf.cmdline - Written
C:\Users\<USER>\AppData\Local\Temp\yhf2hucf.out
Show all 27 entries for files
- Written
C:\Users\<USER>\AppData\Local\Temp\yhf2hucf.err - Written
C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\ModuleAnalysisCache - Written
C:\Users\<USER>\AppData\Local\Temp\nom20ol3.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\nom20ol3.0.cs - Written
C:\Users\<USER>\AppData\Local\Temp\nom20ol3.dll - Written
C:\Users\<USER>\AppData\Local\Temp\nom20ol3.cmdline - Written
C:\Users\<USER>\AppData\Local\Temp\nom20ol3.out - Written
C:\Users\<USER>\AppData\Local\Temp\nom20ol3.err - Written
C:\Users\<USER>\AppData\Local\Temp\CSCB068D3B78254A57958749EBEEBD3ED7.TMP - Deleted
C:\Users\<USER>\AppData\Local\Temp\yhf2hucf.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\yhf2hucf.0.cs - Deleted
C:\Users\<USER>\AppData\Local\Temp\yhf2hucf.out - Deleted
C:\Users\<USER>\AppData\Local\Temp\yhf2hucf.cmdline - Deleted
C:\Users\<USER>\AppData\Local\Temp\yhf2hucf.pdb - Deleted
C:\Users\<USER>\AppData\Local\Temp\yhf2hucf.err - Deleted
C:\Users\<USER>\AppData\Local\Temp\nom20ol3.0.cs - Deleted
C:\Users\<USER>\AppData\Local\Temp\nom20ol3.err - Deleted
C:\Users\<USER>\AppData\Local\Temp\nom20ol3.pdb - Deleted
C:\Users\<USER>\AppData\Local\Temp\nom20ol3.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\nom20ol3.out - Deleted
C:\Users\<USER>\AppData\Local\Temp\nom20ol3.cmdline
Sandbox background — not the file
6The analysis machine's own processes and connections, recorded in every run.
- VM process
conhost.exeC:\Windows\System32\conhost.exe C:\Windows\system32\conhost.exe 0xffffffff -ForceV1 - VM host
edge-mobile-static.azureedge.net - VM host
business.bing.com - VM host
edge-consumer-static.azureedge.net - VM host
www.bing.com - VM host
atm.teams.mira.tm.svc.cloud.microsoft
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache. 9 have no saved verdict and were not checked; that is missing coverage, not a finding.
- f8dbb4274a4db290d620…710c5cNot checkedno saved verdict
- 4b751b7a7415febb467b…7b4037Not checkedno saved verdict
- bf9f958dad8ebdab6321…2d2119Not checkedno saved verdict
- 9f1a49e0c1bbaddca877…87eb1fNot checkedno saved verdict
- eba0270af89b97c752d3…592cbbNot checkedno saved verdict
- ab6aceba7b00505be254…5d4fd5Not checkedno saved verdict
- 31f9305b80ac0531d889…f8a860Not checkedno saved verdict
- 2773c794131dec31ba58…3f9bd2Not checkedno saved verdict
- 912df5d10e8ae77949f1…06dd02Not checkedno saved verdict
Chapter 04
Technical details
None of the 60 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 11, 2026, 2:36 PM UTC
- SHA-256
b1b19c394520bdfe1119058bc7908ff49267c36eebad8d8297e81d3ec9e713a1- SHA-1
6ecf41776facefa4264c9b642ea14de6df9900f5- MD5
da6f13428d57436f33f123e97e4ae39d
About this file
SDF-43.bat is a Powershell file of 11.8 kB.
- Type and size
- Powershell · 11.8 kB
- Signer
- Not applicable
- First seen
- Oct 11, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
First scanned
Antivirus consensus
0 of 60 engines flagged this file
15 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-231 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
- VaristNo result
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootNo result
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
How widely this file has been seen
Rarely uploaded, and first seen more than two weeks ago. Often niche legitimate software or internal tooling; not a strong malware signal on its own.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is SDF-43.bat safe, or is it malware?
What is SDF-43.bat?
How many antivirus engines detected SDF-43.bat?
I already downloaded and ran SDF-43.bat — what should I do?
What is the SHA-256 hash of SDF-43.bat?
How up to date is this analysis of SDF-43.bat?
Community
Member reviews and reports for this exact file hash.