Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Also the Appdata Temp is web based so we can assume its using Node JS.
The interesting File Handles are not particularly interesting at all, they're mostly stock standard stuff that most engines run through, strange that its running so many EXE's but if you're concerned run it through Virus Total.
If its using something like Chromium and NodeJS it requires a simple level of networking to host a local server on.
Most engines run crypto to stop users datamining and then stealing/modding their content.
Also the EXE's aren't really suspiciously named.
device.service - Should find the GPU and CPU
media.service - Runs media files (hence FFMpeg)
data_decoder.service - Decodes game data for use (hence cryptography)
My point being that if you're concerned with programs then run them through a site like VirusTotal and contact the developer to check with them as well. I also recommend you do this scan on any AAA game that is meant to be single-player. You should find some direct references in the way of DLLs and read/write directories.