mirror of
https://github.com/prasathmani/tinyfilemanager.git
synced 2026-04-26 10:55:56 +03:00
[GH-ISSUE #1316] 3/65 security vendors flagged this file as malicious #841
Labels
No labels
Feature
Feature
Is It Really an Issue?
Need More Info
Request
Security
bug
duplicate
enhancement
enhancement
help wanted
invalid
pull-request
question
suggestion
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tinyfilemanager#841
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @smalos on GitHub (May 12, 2025).
Original GitHub issue: https://github.com/prasathmani/tinyfilemanager/issues/1316
While scanning the downloaded file tinyfilemanager.php, 3 out of 65 security vendors flagged it as malicious.
🔗 VirusTotal Report
SHA256:
3455be6f42e55044ac3c834f1924407f32a5c90b547fb5959069bba015f50e7b
Detections:
Trojan:Php/Agent.NV#
Trojan.Agent/PHP!8.12895 (TOPIS:E0:kj7ifrRxtoT)
The issue is not only with this file directly — unfortunately, other software projects that include TinyFileManager as a third-party dependency are also being flagged as malware on SourceForge. This has serious implications for downstream projects and their reputations.
Could you please verify whether these detections are false positives and consider submitting the file for reanalysis or contacting the vendors for delisting?
@smalos commented on GitHub (May 13, 2025):
I’ve isolated the detection to a single attribute in tinyfilemanager.php:
data-option="fullscreen"Changing it to, for example,
data-option="fs"completely prevents ESET-NOD32 from flagging the file. This strongly suggests that their heuristic is literally matching the keyword “fullscreen” (a term commonly abused by malicious scripts) rather than evaluating its context.
I’ve submitted a false-positive report to ESET (per KB141).
@smalos commented on GitHub (May 13, 2025):
Response from the ESET Malware Response Team: