https://bugs.winehq.org/show_bug.cgi?id=49024
--- Comment #4 from marcus-s youtube@marcus-s.de ---
... but do you expect it to protect you from some unwanted things that scripts can do?
Frankly speaking, that is something pretty fundamental - I would like to see such an ability or mechanism in professional grade software. Windows, ironically, does have at least an attempt of such a mechanism that warns users when critical access happens or when system files are changed. In the very least, Wine should have some kind of protection or warning mechanism when a program attempts to access something outside the Wine prefix.
... then (unless the malware is specifically designed for Wine and will exploit host security somehow) no software run in the prefix will be able to do what your describe.
As I said, in performed a test myself on a real machine with a malware specifically designed to target Windows machines. At first, I could not believe this to be the case - but it is true. This is documented and shown in my own video (I speak German though):
https://www.youtube.com/watch?v=37BUwFH_yKI
In another video, the same ability under Wine is demonstrated:
https://www.youtube.com/watch?v=7cUL1HKfTK0
And another one for good measure:
https://www.youtube.com/watch?v=TErrIvyj_lU