GridinSoft Threat Intelligence

redshift4max.dlr file report

Under review File reputation report
MD5 545816c5af3f9da499954124b066eb07
Latest seen 2025-06-17 23:00:44 (11 months ago)
First seen 2025-06-17 23:00:44 (11 months ago)
Size 8 MB
Publisher Autodesk, Inc.
Product 3ds Max

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-06-17 23:00:44 (11 months ago); latest analysis 2025-06-17 23:00:44 (11 months ago).

Publisher context

Company metadata: Autodesk, Inc.. Product metadata: 3ds Max.

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

redshift4max.dlr is a Windows file recorded in the ThreatInfo database. It is associated with 3ds Max. The reported company name is Autodesk, Inc.. The current detection status is Undefined, based on the latest analysis from 2025-06-17 23:00:44 (11 months ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: 3ds Max
Company Name: Autodesk, Inc.
MD5: 545816c5af3f9da499954124b066eb07
Size: 8 MB
First Published: 2025-06-17 23:00:44 (11 months ago)
Latest Published: 2025-06-17 23:00:44 (11 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-06-17 23:00:44 (11 months ago)
%commonappdata%\redshift\plugins\3dsmax\2023

ThreatInfo has observed redshift4max.dlr in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.

Windows 10 100.0%

The most common operating system signal for redshift4max.dlr is Windows 10 with 100.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.

redshift4max.dlr is identified as pe for 64-bit systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 64-bit
Subsystem Windows GUI
Entry point 0x00448a30
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 9293824

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 4800512 bytes · 51.7% of section data
MD5 85a0fcfe14cda66cf3c3e2b45006199f
.rdata 2630656 bytes · 28.3% of section data
MD5 583b5342b3cbc3c3974973377638e85e
.data 645120 bytes · 6.9% of section data
MD5 5604d690a4efbe443fff96854c523c30
.pdata 168960 bytes · 1.8% of section data
MD5 1f23ed4591dd28a81e7dfa759cd13f62
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 fc2f14d81e335ad78fd3a2189af093b9
.rsrc 778240 bytes · 8.4% of section data
MD5 e0d94c1cd562ea3dd01a2b8dee2b7ed3
.reloc 269824 bytes · 2.9% of section data
MD5 d492005639e3d5ba821960662e6aece5

PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.

Report conclusion

This file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 545816c5af3f9da499954124b066eb07.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.