natan_44 — Wpis 1 z 97
Date: May 27, 2026
Source Type: Official Source Code (Analyzed)
Developer: NBM Studios (NBM Digital Ltd)
================================================================================
1. CRITICAL SECURITY VULNERABILITIES (BACKDOORS & RCE)
================================================================================
[CRITICAL] REMOTE CODE EXECUTION (RCE) VIA PICKLE
- Location: zero_hour_assault.py (Line 1224), zhaserver.py (multiple locations)
- Detail: The game uses the Python 'pickle' module to deserialize data received
directly from the network.
- Risk: 'pickle' is inherently insecure. A compromised server or a malicious
developer can send a crafted packet that executes arbitrary commands on the
player's computer (e.g., deleting files, installing real malware, or stealing
browser cookies). This is a built-in backdoor.
[CRITICAL] INSECURE AUTO-UPDATE SYSTEM
- Location: updater.py, main.py
- Detail: Every time the game starts, it checks for updates and automatically
downloads .exe, .dll, and .zip files from nbmstudios.com.
- Risk: There is NO digital signature or hash verification for these downloads.
If the developer's site is hacked, every player's computer will automatically
download and run whatever malicious file the hacker uploads.
[HIGH] PLAINTEXT CREDENTIAL STORAGE
- Location: server/zhaserver.py, server/chars/*/pass.usr
- Detail: The server stores player passwords in raw, plaintext files.
- Risk: No hashing (like bcrypt/argon2) is used. If the server is breached,
every player's password for every account is instantly compromised.
================================================================================
2. DEVELOPER "ACTIVITIES" & PRIVACY (SURVEILLANCE)
================================================================================
HARDWARE TRACKING (COMPUTER ID)
- Location: network.py, net.py, zhaserver.py
- Activity: The game generates a 'compid' (Computer ID) based on hardware
parameters. This is used to link all accounts created by a single person
and enforce bans.
ADMINISTRATIVE SPYING TOOLS
- Location: zhaserver.py (Admin Commands)
- Activity: Administrators have built-in commands to:
* /seemail: View a player's registered email address.
* /listip: View the real IP address of every connected player.
* /viewplayer: View detailed metadata including creation date and inventory.
* /itemlist: Inspect exactly what items a player has.
INVASIVE ANTI-CHEAT (MEMORY SCANNING)
- Location: anticheat.dll (External binary called by zero_hour_assault.py)
- Activity: The anticheat performs memory scanning. While standard for games,
the lack of transparency and the fact that the DLL is downloaded
unverified at runtime is a privacy risk.
EXPOSED SECRETS IN SOURCE CODE
- Telegram Bot Key: [REDACTED]
- Google API Key: [REDACTED]
- Risk: These keys allow anyone with the source code to hijack official
developer communication channels or consume their API quotas.
================================================================================
3. COMMUNITY REPUTATION & DRAMA HISTORY
================================================================================
MALWARE RUMORS (RATs)
- For years, the audiogame community (audiogames.net, elten.link) has
rumored that NBM Studios' software contains Remote Access Trojans (RATs).
The discovery of the 'pickle' vulnerability confirms the *technical*
existence of these capabilities.
IP THEFT (CLONING)
- NBM Studios is frequently accused of stealing code and assets from
other games like "Survive the Wild."
2023 SECURITY BREACH
- In August 2023, the developers admitted to a major "terrible incident"
(server breach) that exposed the inherent insecurity of their platform.
================================================================================
4. FINAL VERDICT & RECOMMENDATIONS
================================================================================
VERDICT: HIGH RISK
The code is functional as a game but is architecturally "toxic" from a
security perspective. It lacks industry-standard protections and includes
logic that functions as a backdoor.
RECOMMENDATIONS FOR USERS:
1. NEVER use the same password for this game as you use for your email/bank.
2. Be aware that the developers (or anyone who hacks them) can technically
control your computer through the 'pickle' network vulnerability.
3. Run the game in a Sandbox or VM if you value your primary system's privacy.
4. Do not trust the "official" nature of the code to mean it is "safe."
================================================================================
REPORT END
================================================================================