Maybe. However sometimes VBox updates really can help - like in case of this bug http://www.kernelmode.info/forum/viewto ... 930#p18930
long time used to detect VBox and fixed only in 4.3.4. What if something like this exists in 4.3.12?
One thing I can certainly say right now - old style vbox dlls patching is dead.
What exactly patching were doing - they removed VirtualBox, Innotek, Oracle, Virtual Machine signatures inside.
Some things can be replaced with DMI configuration - yes, this thread have examples. Do not install VM additions - yes, this is advice by default in case of malware RE on VBox.
But several detection methods does not rely on the above data and cannot be reconfigured anyhow by VirtualBox user. One of it - firmware data that is accessible from Windows or from kernel mode and can be used to reveal VBox easily. Starting with 4.3.14 in the pathetic attempt stop VBox exploitations Oracle made his virtual machine friendly to detection by malware. Success.