Under specific circumstances (such as high-resolution rendering or long rendering timelines), the script may attempt to collect system metadata—like CPU type, RAM capacity, and network info—and try to ping external, non-operational web servers.

You can check for infection by opening the MAXScript Listener (F11) and looking for unusual global variables or scripts running in the background.

If you'd like to troubleshoot a related to V-Ray or check if other startup scripts are safe, let me know!

To prevent vraymatnetprop.mse errors from disrupting your pipeline, implement these workflow habits: