FILEMembers
FILE

Sandbox loader invoked DLL exports; logger write remains unattributed

A sandbox report links several `rundll32.exe` calls to the submitted DLL through their common loader parent. It also records a write of `0` to a kernel logger’s `Status` value, but does not identify the writer or show that tracing stopped.

Nov 16, 2026, 02:56 (UTC+9)Last seenNov 16, 2026Severity77ByCTX TeamActorSafePayIOC15MITRE13RegionsPK

A sandbox DLL loader spawned several rundll32.exe processes naming functions in the same submitted file. Its report also recorded a write of 0 to a Windows kernel logger’s Status value. Did the DLL interfere with logging, or do these observations merely share an analysis report? The records reviewed by CTX Threat Intelligence establish the loader-to-process relationship, but not a causal link to the registry write.

Members only

Members-only article

This story is members-only. Sign in to read the full body, indicators of compromise, and VirusTotal context.

Sign in to read
Source: CTX Threat Intelligence