Windows DLL sideloading abuses an executable's DLL loading behavior: when the application is started, it may load an unintended library placed beside it or in another eligible search location. The result depends on the requested module, load API and flags, Known DLLs, manifests or package dependencies, architecture, and process security context; placing a DLL beside an executable alone does not guarantee it will load. Loaded code runs with the process's security token, so elevated execution is possible only when the launch path already runs with elevated rights.
RESTRICTED_ACCESS_BLUR_MARKER
RESTRICTED_ACCESS_BLUR_MARKER
RESTRICTED_ACCESS_BLUR_MARKER
RESTRICTED_ACCESS_BLUR_MARKER