File verdict·Decided by the MT AI Engine
Our call

Suspicious

Nuitka-compiled Python archive with process-injection and direct-IP contact patterns; weak tier-1 consensus and legitimate infrastructure contact suggest mixed signals.

nuitka
Trust score52Caution
Trinity.zip
42.7 MB
c766dfdaa774a80a4b804e20696e
Antivirus engines
3 of 74 flagged
Code signing
Unsigned
Age
First seen 22 days ago
MT AI Engine · our arbiter

The verdict, reasoned out.

Not a rules engine. The MT AI Engine reads every signal we collected, weighs them against history, and commits to an answer.

62%Confidence
Moderate
Reasoning

The sample exhibits offensive MITRE techniques (T1055 process injection, T1543 system process modification) and contacted external IPs without domain resolution, which are typically malware indicators. However, the evidence is ambiguous: ESET's single tier-1 flag lacks consensus (16 other tier-1 engines clean), the contacted IPs are public infrastructure used for certificate validation, and the dropped DLLs are standard Python runtime libraries. The Nuitka compiler and obfuscation (AGen suffix) suggest intentional packing, but this is common in legitimate penetration-testing and system-administration tools. No malicious sandbox verdict, no external intel corroboration, and no confirmed malicious children weigh against a malicious verdict. The weak tier-1 consensus combined with ambiguous C2 indicators places this in suspicious territory rather than malicious.

Key signals · 5

Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.

  1. ESET-NOD32 (tier-1) flags 'Python/Packed.Nuitka_AGen.MO suspicious application' — named family with obfuscation marker, but only 1/17 tier-1 engines agree (no strong consensus)

  2. triggeredHeuristics: ProcessInjection (T1055, rundll32 + DLL loading) and DirectIpC2 (4 external IPs, zero domains) — both offensive patterns

  3. Contacted IPs are public infrastructure (8.8.8.8 Google DNS, 104.18.38.233 Cloudflare, 162.159.36.2 Cloudflare, 172.64.149.23 Cloudflare) and OCSP certificate-validation URLs — not typical malware C2

  4. Dropped children (10 files) all unknown verdict; no malicious children confirmed; no malicious sandbox verdict recorded

  5. No external intel corroboration (YARAify=0 rules, CIRCL=no hit, MalwareBazaar=no hit); medium prevalence (6 submitters, 7 submissions) suggests emerging or niche tool

Points in its favour
  • 16 of 17 tier-1 engines reported clean — weak malicious consensus
  • Contacted IPs are public infrastructure (Google DNS, Cloudflare) — not typical malware C2
  • No malicious sandbox verdict recorded
  • No external intel corroboration (YARAify, CIRCL, MalwareBazaar)
  • No confirmed malicious dropped children
Points against
  • Process injection via rundll32 (T1055) — payload smuggled into legitimate process
  • Direct-IP contact without domain resolution — bypasses reputation-based blocklists
  • Nuitka obfuscation (AGen suffix) — intentional code packing
  • Unsigned binary — no publisher verification
  • Generic tier-2 and low-trust detections — may indicate heuristic false positives
What to do

Treat this file as suspicious and avoid execution unless you can verify its origin and purpose from a trusted source. If already executed, monitor for unexpected process-injection activity or network connections to unfamiliar hosts. Consider submitting the sample to your security team for manual analysis.

Threat family attribution

nuitka corroborated by 2 sources

  • VT (74 engines)
    nuitka
  • MT AI Engine
    nuitka
Runtime behaviour

What this file did when executed

This file was detonated in 1 sandbox and its runtime behaviour was observed.

MITRE ATT&CK
21

Adversary techniques mapped to the MITRE ATT&CK framework.

T1027T1033T1055T1057T1059T1071T1074T1082T1105T1106T1112T1129T1202T1497T1539T1543T1547T1562T1562.001T1573T1574
Spawned processes
15
$(unnamed)
"C:\Users\<USER>\AppData\Local\Temp\AmcacheParser.exe"
$(unnamed)
"C:\Users\<USER>\AppData\Local\Temp\AppCompatCacheParser.exe"
$(unnamed)
"C:\Users\<USER>\AppData\Local\Temp\JLECmd.exe"
$(unnamed)
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\libcrypto-1_1.dll",#1
$(unnamed)
C:\Windows\system32\WerFault.exe -u -p 5452 -s 544
$(unnamed)
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\libffi-8.dll",#1
$(unnamed)
C:\Windows\system32\WerFault.exe -u -p 2632 -s 576
$(unnamed)
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\libssl-1_1.dll",#1
+7 more processes captured.
Network activity
9
IP addresses4
  • 8.8.8.8
  • 104.18.38.233
  • 172.64.149.23
  • 162.159.36.2
URLs5
  • http://ocsp.sectigo.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBSdE3gf41WAic8Uh9lF92%2BIJqh5qwQUMuuSmv81lkgvKEBCcCA2kVwXheYCEGIdbQxSAZ47kHkVIIkhHAo%3D
  • http://ocsp.sectigo.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBQVD%2BnGf79Hpedv3mhy6uKMVZkPCQQUDyrLIIcouOxvSK4rVKYpqhekzQwCEAajmICyUarJo3PdWocUg94%3D
  • http://ocsp.sectigo.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBSdE3gf41WAic8Uh9lF92+IJqh5qwQUMuuSmv81lkgvKEBCcCA2kVwXheYCEGIdbQxSAZ47kHkVIIkhHAo=
  • http://ocsp.comodoca.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBRTtU9uFqgVGHhJwXZyWCNXmVR5ngQUoBEKIz6W8Qfs4q8p74Klf9AwpLQCEEj8k7RgVZSNNqfJionWlBY=
  • http://ocsp.sectigo.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBQVD+nGf79Hpedv3mhy6uKMVZkPCQQUDyrLIIcouOxvSK4rVKYpqhekzQwCEAajmICyUarJo3PdWocUg94=
Filesystem & mutexes
40
Files written15
  • C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\AmcacheParser.exe.log
  • C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\AppCompatCacheParser.exe.log
  • C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\JLECmd.exe.log
  • C:\ProgramData\Microsoft\Windows\WER\Temp
  • C:\ProgramData\Microsoft\Windows\WER\Temp\d677da13-cb2a-45f6-9043-9c17424ecd8f
+10 more
Files deleted15
  • C:\ProgramData\Microsoft\Windows\WER\Temp\WER94D8.tmp
  • C:\ProgramData\Microsoft\Windows\WER\Temp\WER9CC8.tmp
  • C:\ProgramData\Microsoft\Windows\WER\Temp\WER9EDD.tmp
  • C:\ProgramData\Microsoft\Windows\WER\Temp\WER94D8.tmp.dmp
  • C:\ProgramData\Microsoft\Windows\WER\Temp\WER9CC8.tmp.WERInternalMetadata.xml
+10 more
Mutexes created10
  • Local\WERReportingForProcess5452
  • Global\1f08316a-edbc-4e31-959c-779198068d14
  • Local\WERReportingForProcess2632
  • Global\d2f0f394-1010-4a90-9508-d8b39dbb4724
  • Local\WERReportingForProcess5636
+5 more
Dropped payload

Files this sample writes at runtime

This file drops 10 children at runtime. None are currently flagged malicious in our cache.

10 unseen
  • 3e363bf82545f24cce8c308a5dNever scanned
    never seen before
  • 48f4a239c25354f0e9f817ecedNever scanned
    never seen before
  • 359c9c02a9fa3de10ba452ab21Never scanned
    never seen before
  • e9b7aecd456f1d228860b73ec2Never scanned
    never seen before
  • 20139f4c327711baf18272ed94Never scanned
    never seen before
  • 3271d39d7b4dcd841e8eefe5e5Never scanned
    never seen before
  • cb71909bf01a3a7a4c73d46e13Never scanned
    never seen before
  • 9fac69dc609cc6074ecdfc54f6Never scanned
    never seen before
  • e65d6e5e837df0a2df0d2d9d6cNever scanned
    never seen before
  • 98074c85650a420a095ab084e9Never scanned
    never seen before
No researcher-database hits
External threat-intel sources were not collected for this scan.
Signature matches

YARA + heuristic rules that fired

A researcher-curated or high-severity heuristic rule matched this sample. These rules target specific malware families and are near-definitive.

2 synthesis
MITRE ATT&CK profile
Defense evasion× 1C2× 1
MalwareTips synthesis rules
Our heuristics on VT data + sandbox behaviour
  • ProcessInjectionhigh

    MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.

    Evidence
    "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\libcrypto-1_1.dll",#1
  • DirectIpC2medium

    Sample contacted 4 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.

    Evidence
    8.8.8.8 · 104.18.38.233 · 172.64.149.23
Antivirus engine breakdown

3 detections across 74 engines

3 malicious0 suspicious71 clean
Tier-117 engines
1flag
Top commercial AVs (low FP rate)
Tier-240 engines
1flag
Mainstream engines with mixed FP rates
Low-trust17 engines
1flag
Heuristic / generic-AI engines (high FP rate)
ESET-NOD32
malicious
Python/Packed.Nuitka_AGen.MO suspicious application
TrellixENS
malicious
Artemis!F1FEF6A2DB89
Webroot
malicious
Win.Malware.Gen
Hash c766dfdaa774… cross-referenced against 74 AV engines via our AV network.
Prevalence

How often this file shows up in the wild

Moderate prevalence — neither rare nor common. No strong prior applies.

Medium
Unique uploaders
6
Moderate upload volume.
Total submissions
7
Includes repeat uploads by the same source.
First seen by VT
21d ago
Jun 19, 2026
Prevalence quadrant
Rare · New
Targeted malware lives here
Common · New
Just-released software
Rare · Old
Niche or internal tooling
Common · Old
Trusted legitimate binaries
File identity

Forensic fingerprint

File biography
First seen (VT)
6/19/2026, 12:06:18 PM
First seen (MalwareBazaar)
Last analysis (VT)
6/19/2026, 12:06:18 PM
Scanned here
7/11/2026, 12:19:29 AM
File name
Trinity.zip
Size
42.67 MB
MIME type
(unknown)
Detected type
ZIP
SHA-256
c766dfdaa774a80a4bcdfddf679ec2a09d8b372fe03c7e5b13e165804e20696e
MD5
3f7734d235366be39fcdb2c575ba8962
SHA-1
0b1708707fa04560e80e05920d318cd56062c5af
First seen (VT)
6/19/2026, 12:06:18 PM
Last analysis (VT)
6/19/2026, 12:06:18 PM
First scan (MalwareTips)
7/11/2026, 12:19:29 AM
Last scan (MalwareTips)
7/11/2026, 12:19:29 AM
Behavior tags
contains-pezipdetect-debug-environmentlong-sleeps
Frequently asked

Safety FAQ

Common questions about Trinity.zip, answered from the scan data above.

  • Trinity.zip is suspicious — treat it as unsafe until you're sure. 3 of 74 antivirus engines flag it (family: nuitka), which isn't a strong consensus but is enough to be cautious. Don't opened or extracted it unless you fully trust where it came from, and prefer downloading the software fresh from its official site.
  • Trinity.zip is a compressed archive, about 42.7 MB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
  • 3 of 74 antivirus engines flagged Trinity.zip, 3 of them as outright malicious. A small number of detections can include false positives, so we weigh which engines flagged it and what else the file does, not just the raw count.
  • Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
  • To remove Trinity.zip: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete the original Trinity.zip file and empty the Recycle Bin/Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
  • Trinity.zip is flagged as malicious (family: nuitka). Engines attribute it to the nuitka family. Knowing the family matters because it tells you the likely impact — data theft, remote control, file encryption, or unwanted ads — and guides the cleanup.
  • The SHA-256 hash of Trinity.zip is c766dfdaa774a80a4bcdfddf679ec2a09d8b372fe03c7e5b13e165804e20696e, and its MD5 is 3f7734d235366be39fcdb2c575ba8962. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
  • This report reflects the scan run on July 11, 2026. Because a file's hash never changes, the identity of Trinity.zip is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Community classification

Reviews & malware reports(0)

Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.

Loading…
Loading reports…
Files are processed in a streaming pass-through — MalwareTips never stores the binary on its servers. Only the scan result (hash, detections, verdict) is retained so the next person who scans the same file gets an instant answer. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.