Fix vuln unique ID logic

[Nitr4x]

Description

Splitting the hash strategy per engine.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that causes existing functionality to change)
• Documentation update
• Refactor / code cleanup
• CI / build change

How Has This Been Tested?

# Example
go test ./...

Checklist

• My code follows the project's coding standards (go vet ./... passes)
• I have run the existing test suite and all tests pass (go test ./...)
• I have added or updated tests that cover my changes
• I have updated documentation where relevant (README, comments, etc.)
• I have not introduced new secrets, credentials, or sensitive data
• My changes do not break backward compatibility (or I have documented breaking changes above)

Screenshots / Output (if applicable)

N/A