GridinSoft Threat Intelligence

redshift4max.dlr file report

Under review File reputation report
MD5 da4f23d4c5703e31a0917b0e0d2d070e
Latest seen 2025-06-17 23:00:37 (11 months ago)
First seen 2025-06-17 23:00:37 (11 months ago)
Size 10 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:37 (11 months ago); latest analysis 2025-06-17 23:00:37 (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:37 (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: da4f23d4c5703e31a0917b0e0d2d070e
Size: 10 MB
First Published: 2025-06-17 23:00:37 (11 months ago)
Latest Published: 2025-06-17 23:00:37 (11 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-06-17 23:00:37 (11 months ago)
%commonappdata%\redshift\plugins\3dsmax\2018

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 0x004c71f0
Image base 0x0000000180000000

PE Sections:

Sections 9
Raw data 10961920

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

.text 5481472 bytes · 50.0% of section data
Large raw data
MD5 9fc1b8adf9aebd7db3fae316148a4cf6
.rdata 3545600 bytes · 32.3% of section data
MD5 7ea5c4ce2967bf491da30af61c31120f
.data 608256 bytes · 5.5% of section data
MD5 d965a07ee126202b20e02402ec31e8a6
.pdata 244736 bytes · 2.2% of section data
MD5 f961079665aa02a7b0e1979d823c4d5f
.gfids 512 bytes · 0.0% of section data
Uncommon name
MD5 1411b7587a7e8ce74839ce7d42783d7d
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
_RDATA 32768 bytes · 0.3% of section data
Uncommon name
MD5 6d14eb7565726750bb0df2c22b188ee5
.rsrc 778240 bytes · 7.1% of section data
MD5 dc33f05fc1ce1a57deb65371cab46963
.reloc 269824 bytes · 2.5% of section data
MD5 de8b86363e4f67afcf30ffdc91e443e5

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 da4f23d4c5703e31a0917b0e0d2d070e.
  • 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.