
Sandbox records two HTTPS POSTs to a malicious file’s /api endpoint
Two POST requests to the same HTTPS path received reported HTTP 200 responses, making this the clearest recorded web exchange associated with the Windows executable. The requests and responses do not reveal what the endpoint did, while other linked domains have only TLS or DNS evidence.
Two HTTPS POST requests to deadpanstupiddyjjuwk.shop/api received HTTP 200 responses in a sandbox report for a malicious Windows executable. That is more informative than a domain appearing in a threat list: it records an application-level exchange with a specific path. But what role did that endpoint play, and do the other domains associated with the file have equally strong evidence behind them?
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