GridinSoft Threat Intelligence

redshift4max.dlr file report

Under review File reputation report
MD5 d9c99cc8a26a3b4ad9c7e75115390218
Latest seen 2026-02-03 23:01:12 (3 months ago)
First seen 2026-02-03 23:01:12 (3 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 2026-02-03 23:01:12 (3 months ago); latest analysis 2026-02-03 23:01:12 (3 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 2026-02-03 23:01:12 (3 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: d9c99cc8a26a3b4ad9c7e75115390218
Size: 8 MB
First Published: 2026-02-03 23:01:12 (3 months ago)
Latest Published: 2026-02-03 23:01:12 (3 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-02-03 23:01:12 (3 months ago)
%commonappdata%\redshift\plugins\3dsmax\2021

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

PE Sections:

Sections 7
Raw data 9425408

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

.text 4639744 bytes · 49.2% of section data
MD5 f7d2a0c0eb521abd9b5c785131b111ba
.rdata 2959872 bytes · 31.4% of section data
MD5 5e33a59c452ad224a8f4915883d96c27
.data 600064 bytes · 6.4% of section data
MD5 591181549e180f993cf7194b190750e2
.pdata 172032 bytes · 1.8% of section data
MD5 43006cac2698a13b1a15bf1392c93a32
_RDATA 38912 bytes · 0.4% of section data
Uncommon name
MD5 917e4b53211ff5aa7ad53c6479fd16b0
.rsrc 775168 bytes · 8.2% of section data
MD5 0da5500acc74161aaaf9bf07b5a3cca0
.reloc 239616 bytes · 2.5% of section data
MD5 33dbab37aefce80c2d7f6bef1a013f16

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