Is TGMacro.v3.053.Portable.zip safe?
Only VBA32 flagged the archive among 75 engines, but process-injection and LSASS-related runtime indicators justify caution until the embedded executables are independently verified.
The antivirus result strongly resembles a false positive: only VBA32 detected a generic MSIL trojan, while all 17 tier-1 engines were silent. However, one sandbox recorded process-injection, service-related, defense-evasion, and LSASS-targeting indicators, so the archive should not be trusted solely from the scan ratio.
e39c2558d8fef8112a…fc484594c0e15fRecommended next actions
Before opening or extracting
Do not open or extract it until the source can be verified independently.
If you already opened or extracted it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
The antivirus result strongly resembles a false positive: only VBA32 detected a generic MSIL trojan, while all 17 tier-1 engines were silent. However, one sandbox recorded process-injection, service-related, defense-evasion, and LSASS-targeting indicators, so the archive should not be trusted solely from the scan ratio.
Only 1 of 75 engines flagged the archive, and that result came from VBA32 with the generic label TScope.Trojan.MSIL. All 17 tier-1 engines reported no detection, creating a strong low-trust-only false-positive pattern. One completed sandbox run nevertheless mapped activity to T1055, T1543, and T1562.001, with an additional LSASS-targeting indicator. The sandbox did not issue a malicious verdict, and none of four inspected dropped files was identified as malicious, although all four child verdicts remained unresolved. Host-reputation coverage included every distinct observed domain, IP address, and URL and found no known-malicious or suspicious hosts. The runtime concerns therefore merit isolation and verification, but they do not establish a named malware family.
What We Detected
VBA32 was the only detector among 75 engines, reporting the generic label TScope.Trojan.MSIL. No tier-1 engine flagged the archive, and there was no family consensus or confirmed hacktool label. The file is also widely submitted, with 866 sources accounting for 1,100 submissions.
Threat Behavior
One sandbox run recorded MITRE techniques T1055, T1543, and T1562.001. The evidence includes rundll32.exe loading SDL2.dll from a temporary directory and an LSASS-targeting indicator, both of which deserve caution. However, the sandbox produced no malicious verdict, all observed hosts received complete reputation coverage without known-malicious or suspicious results, and no inspected dropped child was identified as malicious. The four child files still have unresolved verdicts, so their absence of a malicious classification is not proof that they are benign.
What To Do Now
Keep endpoint protection enabled and avoid running the archive on a production system until the embedded executables are scanned separately and their source is verified. If execution is necessary, use an isolated test environment and monitor for unexpected LSASS access, service creation, or process injection.
Where this verdict could be wrong3 caveats
- MalwareTips.Synth.ProcessInjection fired on rundll32.exe loading SDL2.dll and maps the activity to T1055, which warrants caution despite weak antivirus corroboration.
- MalwareTips.Synth.CredentialDumper reports activity targeting lsass.exe; this is concerning, although the sole sandbox did not issue a malicious verdict.
- VBA32 labeled the archive TScope.Trojan.MSIL, but it is the only detector among 75 engines and is low-trust in this result.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1/75 engines detected the file, and the sole detector was low-trust.
- All 17 tier-1 engines reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false.
- Complete contacted-host coverage found 0 known-malicious and 0 known-suspicious hosts.
- YARAify, CIRCL, and MalwareBazaar provided no corroborating hit.
- One sandbox recorded MITRE T1055 process-injection activity.
- A heuristic reported LSASS-targeting behavior associated with credential access.
- MITRE T1543 and T1562.001 indicate service-related and defense-evasion activity.
- Four dropped child files have unresolved verdicts.
- The archive is not covered by executable code-signing verification.
Keep security software enabled and quarantine the archive until its embedded executables can be verified separately. Obtain it only from the developer's official release channel and avoid entering sensitive credentials while testing.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 of 40 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 22MITRE ATT&CK techniques
- 15spawned processes
- 41network contacts
- 27filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Created or modified a system service, which can keep code running.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
TGMacro.v3.053.Portable.zip
e39c2558d8fef8112a12576e73e8b992dcbd670d2959a32dfbfc484594c0e15f
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\SDL2.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\TGMacro.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
settings.json
C:\Users\<USER>\AppData\Local\Temp\settings.json
04Isolated runtime analysis - Written fileObserved
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
gettgmacro.com
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
trksyln.net
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- gettgmacro.com
- trksyln.net
- edge-mobile-static.azureedge.net
- business.bing.com
- fundingchoicesmessages.google.com
- pagead2.googlesyndication.com
- googleads.g.doubleclick.net
- www.gstatic.com
- analytics.google.com
- xpaywalletcdn.azureedge.net
- 187.124.10.244
- 150.171.110.195
- 150.171.73.13
- 192.178.129.101
- 74.125.126.94
- 173.194.64.102
- 142.251.183.132
- 142.250.152.155
- 74.125.201.132
- 173.194.195.132
- https://gettgmacro.com/manifest.json
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP.NET_4.0.30319\Names\1RM7u00EugDEmhVlRN6keFSHqOBNBfXE41rBsHTpZUzV3C9EOoJEzfPShYBVNCcKyaIGlBYxoF4s3sQxlTiGLWah6EAfEZ0BS1JoA9sOvlJfHBA2OJuPXJ
- Software\Microsoft\Internet Explorer\TabbedBrowsing\NTPDaysSinceLastAutoMigration
- Software\Microsoft\Internet Explorer\TabbedBrowsing\NTPLastLaunchLowDateTime
- Software\Microsoft\Internet Explorer\TabbedBrowsing\NTPLastLaunchHighDateTime
- Software\Microsoft\Internet Explorer\UrlBlockManager\NextCheckForUpdateLowDateTime
- Software\Microsoft\Internet Explorer\UrlBlockManager\NextCheckForUpdateHighDateTime
- C:\Users\<USER>\AppData\Local\Temp\settings.json
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\Users\<USER>\AppData\Local\Temp\edge_BITS_1828_1011675573\BIT3B98.tmp
- C:\Users\<USER>\AppData\Local\Temp\edge_BITS_1828_1011675573\fef489f0-c0aa-4886-ba2b-137e93d55624
- C:\Users\<USER>\AppData\Local\Temp\edge_BITS_1828_272709587\BIT5C5F.tmp
- C:\Users\user\AppData\Local\Google\Chrome\User Data\Default\597cce38-3083-439f-810a-81c4f185a0f5.tmp
- C:\Users\user\AppData\Local\Google\Chrome\User Data\Local State~RF5cc7f.TMP
- trksyln-TMACRO
- Local\!BrowserEmulation!SharedMemory!Mutex
- Local\VERMGMTBlockListFileMutex
- Local\URLBLOCK_FILEMAPSWITCH_MUTEX_2084
- Local\URLBLOCK_HASHFILESWITCH_MUTEX
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- 68c78590d1997122c30c…101d70Never scannednever seen before
- 5e066c9fa8080fd1e213…11afc5Never scannednever seen before
- 9e23b9693a9369a6e0f3…92ba89Never scannednever seen before
- cb58574c0c8b1dd114b9…ad9a5cNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 1 / 75engines flagged
- 866sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
1 of 75 antivirus engines flagged the file, including VBA32.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1,100 times from 866 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: TGMacro.v3.053.Portable.zip — e39c2558d8fef8112a12576e73e8b992dcbd670d2959a32dfbfc484594c0e15f
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\SDL2.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\TGMacro.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: settings.json — C:\Users\<USER>\AppData\Local\Temp\settings.json
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Download-1.tmp — C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: gettgmacro.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: trksyln.net — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\SDL2.dll",#1Sandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exe
1 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- TGMacro.v3.053.Portable.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 937.9 KB
- Last analyzed
- Sep 27, 2026, 11:57 PM UTC
e39c2558d8fef8112a12576e73e8b992dcbd670d2959a32dfbfc484594c0e15fSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't open or extract it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this archive and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is TGMacro.v3.053.Portable.zip safe, or is it malware?
What is TGMacro.v3.053.Portable.zip?
How many antivirus engines detected TGMacro.v3.053.Portable.zip?
I already downloaded and opened or extracted TGMacro.v3.053.Portable.zip — what should I do?
How do I remove TGMacro.v3.053.Portable.zip?
What is the SHA-256 hash of TGMacro.v3.053.Portable.zip?
How up to date is this analysis of TGMacro.v3.053.Portable.zip?
Community
Member reviews and reports for this exact file hash.