File scan report
Verdict Safe
Is super-
This Python stress-test script drew no detections from any of 76 engines, and sandbox runs showed only ordinary activity with no reputation-flagged network contacts.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
This script can be used as intended; expect heavy resource usage while a stress test runs, and keep your security software enabled.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your security software and system updates switched on.
No scanner can promise a file is 100% safe.
Antivirus results
0 of 63 flagged
- Flagged 0
- No detection 63
- No result 13
- Code signing Not applicable
- Test run Completed
- First seen 1y ago
Chapter 02
Why we think so
0 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 63 antivirus engines that checked it flagged this Python script. Two sandbox runs recorded only techniques common in legitimate software and contacted GitHub's raw content host and the Snapcraft API, neither of which has a malicious reputation. No threat-intelligence database lists it.
None of the 63 antivirus engines that checked it flagged the script, including all 18 major antivirus engines that analysed it. Two sandbox runs on Windows and Linux simply launched the script with Python and recorded only techniques common in legitimate software, with no process injection, persistence or dropped files. Its network contacts were GitHub's raw content host and the Snapcraft API, and all four observed hosts were checked with no malicious or suspicious reputation. No public malware databases or community rules list the file, and it has been seen by 20 submitters over about a year and a half.
What We Detected
None of the 63 antivirus engines that checked it flagged this Python script, and no malware database or community rule set lists it. It has circulated for around 556 days among 20 submitters.
Threat Behavior
Two sandbox runs executed the script with Python on Windows and Linux. They recorded only techniques common in legitimate software, such as system information discovery and web requests, with no injection into other processes, no persistence and no dropped files. The script contacted GitHub's raw content host and the Snapcraft API; all observed hosts were checked and none has a malicious or suspicious reputation.
What To Do Now
The evidence supports running this script if you need it. As a stress test it may push CPU or memory usage high, so run it when you can tolerate heavy load and close it if your system becomes unresponsive.
Where this verdict could be wrong1 caveat
- The script was not uploaded for our own static analysis, so its source code was not reviewed directly; a stress-test script may also consume heavy CPU or memory by design.
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 detections from any of 76 antivirus engines, including all major antivirus engines
- Sandbox runs showed only techniques common in legitimate software
- All contacted hosts were checked and none has a bad reputation
- No listing in public malware databases or community rule sets
- Seen by 20 submitters over roughly a year and a half
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 2 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 2isolated sandbox runs
- 4sandbox rule tags
- 4spawned processes
- 4network contacts
- 5filesystem & mutex artifacts
Includes the sandbox verdicts, 4 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
None of the 63 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 22, 2026, 2:13 AM UTC
- SHA-256
8d39af63946cca2943405febcb9a8e60f86eff1a8d29e05b27df8ea6f8038433- SHA-1
965db26f9e40474a6e1d19703c84bac704a250fb- MD5
6cd5efe044a7bf6f5853aa273f91e5bf
About this file
super-python-stress-test.py is a Python file of 45.2 kB.
- Type and size
- Python · 45.2 kB
- Signer
- Not applicable
- First seen
- Apr 13, 2025On VirusTotal.
- Submitted by
- 20 distinct sources
First scanned
Includes every engine result (76) and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is super-python-stress-test.py safe?
What is super-python-stress-test.py?
How many antivirus engines detected super-python-stress-test.py?
What is the SHA-256 hash of super-python-stress-test.py?
Is it safe to run super-python-stress-test.py?
How up to date is this analysis of super-python-stress-test.py?
Community
Member reviews and reports for this exact file hash.