Marcus,
Thanks for reporting this. We actually discovered this issue recently and will be moving those images to a front-end location in the v5.1.2 release. We're anticipating that release to be out around the middle of September with this, and a few other minor fixes.
If you need a solution before then, let me know, and we can tell you the code that you'd need to edit to change that location.
Thanks for the report,
Alex