Technical assessment
The artifact is a README and Dockerfile providing a test environment setup for CVE-2025-34299. It describes the vulnerability and how to verify the vulnerable endpoint is reachable, but contains no exploit or scanner code.
Backdoor review
No backdoor observed in reviewed code
The repository contains only a Dockerfile and a README.md for setting up a vulnerable Monsta FTP test environment. No executable payload, obfuscated code, or concealed behavior is present. The Dockerfile downloads a known vulnerable version of Monsta FTP and the README provides standard documentation and testing instructions. No backdoor, trojan, or suspicious behavior is observed.
Model confidence95%
AuthenticationNot required
LanguagesDockerfileMarkdown
Target softwareMonsta FTP
Attack typesRemote Code ExecutionArbitrary File Upload
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidenceClassification basis and observed behavior
Classification basis
The artifact consists of a Dockerfile that sets up a vulnerable Monsta FTP instance and a README that documents the vulnerability and provides a manual verification curl command. It does not contain any code that automatically exploits the vulnerability or scans for it; it is a technical writeup with setup instructions.
README.md:1-89Dockerfile:1-28Requirements
- A running instance of Monsta FTP version 2.10.4 (vulnerable) is required for testing.
README.md:63
Observed behavior
- The README instructs users to send a POST request to the vulnerable API endpoint to verify it is reachable, expecting a CONNECTION_FAILURE_ERROR response.
README.md:52-58
Safety-review evidenceBehaviors behind the backdoor verdict
Observables
- Vulnerable Software Deployment
- Monsta FTP 2.10.4 downloaded from web.archive.orgThe Dockerfile installs a vulnerable version of Monsta FTP for testing purposes, consistent with the stated CVE-2025-34299 lab intent.
Dockerfile:17-20 - Api Endpoint Disclosure
- /mftp/application/api/api.phpThe README documents the vulnerable API endpoint and provides a curl command to test it, which is normal for a PoC lab environment.
README.md:18-23README.md:52-55
Review boundariesWhat the analysis did not establish
- Only 2 of 5 files in the repository are included in the evidence; 3 files are omitted.
- The evidence does not include any executable exploit or scanner code, only documentation and a Dockerfile.
- Three files in the repository (total 5 files) were omitted from the text evidence and not reviewed; their metadata indicates they are not executable source code.
- The downloaded Monsta FTP zip file is not included in the evidence and was not analyzed for pre-existing backdoors, but the Dockerfile retrieves it from a public archive URL with no modification.
Model interpretationThis review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.