As an update to this for future eyes, turns out there's somehow two resources that have exactly the same URN yet refer to two different resources. This could make sense if it was in the middle of replacing a security group that had dependents and failed, but then I'd question why it even attempted to delete them in the first place.