File scan report
Verdict Suspicious
Is Pixel Cage. exe safe? Treat it as suspicious.
Unsigned 64-bit executable with four less reliable detections and mixed prior import-table fingerprint verdicts.
Read the whole reasonShow less
Why Suspicious? 4 antivirus engines flag it, but no major engine agrees; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Treat the file as untrusted; isolate and analyse further before any production use.
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
4 of 70 flagged
- Flagged 4
- No detection 66
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 6mo ago
Chapter 02
Why we think so
3 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Four less reliable engines flagged the file while major antivirus engines remained silent. Samples built with the same import table have produced both suspicious and malicious verdicts in the past. No sandbox malice or external-intel hits were observed.
The file is unsigned and carries only less reliable detections, yet the import-table fingerprint has previously appeared in samples that received malicious verdicts. Medium prevalence and a single sandbox run showing only routine behaviour leave the risk profile ambiguous. The absence of major consensus and external-intel corroboration prevents a malicious classification, while the unsigned status and prior import-table fingerprint hits prevent a safe classification.
What We Detected
Four less reliable engines (APEX, Bkav, Cylance, Skyhigh) reported the sample; no major antivirus engines raised an alert. The binary is unsigned and shows no packer evidence despite high entropy in the resources section.
Threat Behavior
One sandbox execution recorded nine MITRE techniques common in legitimate software and no offensive techniques. No domains, IPs, or URLs were contacted, and no malicious programs it started or dropped files were observed.
What To Do Now
Do not execute the file on production systems. If the file is required, run it only in an isolated virtual machine and monitor for unexpected network or file-system activity.
Where this verdict could be wrong1 caveat
- Skyhigh smaller detection 'BehavesLike.Win64.Dropper.tc' is a generic behavioural label rather than a named family.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No major detections
- No sandbox malice observed
- No external-intel hits
- Unsigned executable
- Less reliable engine detections
- Prior import-table fingerprint matches linked to malicious samples
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- 9sandbox rule tags
- 2spawned processes
- 0network contacts
- 0filesystem & 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: Checked whether it was running on a test computer.
Note: Listed the programs running on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
Note: Loaded extra code modules while running.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.
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 3: FileSeen in the test run
PixelCage.exe
69cccfac7b923957e0abd4e80da3367ae846b68268eef3714dd6391fd72cfd2c
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 3: ProcessSeen in the test run
PixelCage.exe
"C:\Users\<USER>\Desktop\PixelCage.exe"
Test run - Evidence 3 of 3: ProcessSeen in the test run
PixelCage.exe
"C:\Users\user\Desktop\PixelCage.exe"
Test run - +1 more recorded observation
3 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
9MITRE 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.002· Obfuscated code
- T1057· Lists programs
- T1059· Runs commands
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1129· Loads modules
- T1497.001· Sandbox evasion
Observed activity
Processes started
2Programs the file ran, with their command lines.
PixelCage.exe"C:\Users\<USER>\Desktop\PixelCage.exe"PixelCage.exe"C:\Users\user\Desktop\PixelCage.exe"
Chapter 04
Technical details
4 of the 70 antivirus engines that checked it flag it; no publisher signature.
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.
Engines that flagged it 4
- APEXMalicious
- BkavW32.Malware.761E5559
- CylanceUnsafe
- SkyhighBehavesLike.Win64.Dropper.tc
File fingerprint
- Last analyzed
- Aug 25, 2026, 8:49 PM UTC
- SHA-256
69cccfac7b923957e0abd4e80da3367ae846b68268eef3714dd6391fd72cfd2c- SHA-1
431f471ada587676815c4610b874a7294647f03f- MD5
571ae5dc8ed40a4344fbd67739b4e532
About this file
PixelCage.exe is a Win32 EXE file of 10.0 MB.
- Type and size
- Win32 EXE · 10.0 MB
- Signer
- UnsignedNo code signature.
- First seen
- Apr 23, 2026On VirusTotal.
- Submitted by
- 20 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned
Antivirus consensus
4 of 70 engines flagged this file
5 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-117 engines0flagged
- Tier-236 engines1flagged
- Low-trust17 engines3flagged
View all 75 engine results
- APEXMalicious: Malicious
- BkavMalicious: W32.Malware.761E5559
- CylanceMalicious: Unsafe
- SkyhighMalicious: BehavesLike.Win64.Dropper.tc
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
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.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is PixelCage.exe safe, or is it malware?
What is PixelCage.exe?
How many antivirus engines detected PixelCage.exe?
What should I do if I already ran PixelCage.exe?
What is the SHA-256 hash of PixelCage.exe?
How up to date is this analysis of PixelCage.exe?
Community
Member reviews and reports for this exact file hash.