EXE from deploytool can be cracked by unzipping it

SITUATION: I created a stand-alone EXE file using deploytool. By right-clicking on the EXE and selecting "unzip", it is possible to retrieve the set of files from which the EXE is built upon. It's true that the contents of the .m files result obfuscated, but still one can simply type 'help' to any function within unzipping folder and details are displayed. Furthermore, my application includes a .mat file which can be after unzipping imported/loaded into Matlab with no hassle. QUESTION IS: How can I secure my code from this and prevent the user to get quite a lot of it just by unzipping the EXE file? Thanks.

[Adam]

You don't even need to unzip to see these files. They are all copied onto the user's machine into some location that I can't remember somewhere under the user directory I think. This did bother me at one point too, but as the m files were not readable I stopped concerning myself about it. To load a .mat file a user needs to actually have Matlab installed though. I've never really found any good way to wrap better security around Matlab deployed executables though. Maybe someone has...

[Walter Roberson]

Some aspects of the MATLAB .mat file format are documented, and there are tools that can analyze them.

[BeeTiaw]

I am wondering if this is still possible in 2018?

I built a matlab EXE using deploytool and wondering if it is still possible to crack it and see the m-file?

[Walter Roberson]

Mat files are not encrypted when they are placed in a compiled exe.

See also https://www.mathworks.com/matlabcentral/answers/43896-encryption-of-mat-files