Namespace hijack is the misuse of a trusted naming space, such as a package name, publisher namespace, or organization prefix, to make a malicious or unwanted package appear legitimate. Attackers may register a lookalike name, reuse a copied description, or take advantage of a namespace that users already associate with a reputable project.
This matters in cyber security because many install decisions rely on identity cues before any code is inspected. In package registries, extension stores, and dependency managers, a convincing namespace can trick developers, automated build systems, or security tools into trusting the wrong artifact. Real attacks use this tactic for phishing, malware delivery, or reconnaissance, while defenses focus on strong publisher verification, provenance checks, allowlists, and careful review of new dependencies. Reducing automatic trust in names alone is a key supply-chain defense.


