India Location Normalizer RE-India

• Outcome: Pass
• Latest audit: May 28, 2026, 6:47 AM
• Version:
  1.0.1

Overview

This is a narrow, local-only helper for normalizing Indian real-estate locations, with the main risk being possible data-quality mistakes from ambiguous aliases.

Safe to install for assisted lead-location cleanup. Before relying on it for automated routing, scoring, analytics, or storage, review ambiguous aliases and make downstream steps respect low-confidence or unresolved outputs.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (2)

Vague Triggers

Medium

• Confidence: 88% confidence
• Finding: This JSON contains aliases that are overly broad shorthand terms, which can cause the normalizer to resolve user input to the wrong locality without sufficient context. In a lead-processing pipeline, that can silently corrupt structured location data, causing downstream scoring, routing, or analytics decisions to act on inaccurate geography.

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: Single-token aliases like "thane," "borivali," "malad," "kandivali," and "bandra" collapse distinct east/west areas into one canonical target, creating a data integrity flaw rather than a code execution issue. Because this skill is meant for normalization in a non-write pipeline, the main risk is misclassification of leads and incorrect downstream business actions, especially when location determines territory ownership or priority.

VirusTotal

62/62 vendors flagged this skill as clean.