A name that looks internal is not a trust signal if npm can resolve it from the public registry. In this campaign, the package itself is the lure, and install time is the handoff: the malicious code runs before anyone reviews what it does, so developer hosts and CI jobs can leak environment data and credential context as part of a routine dependency install.
Microsoft says 33 malicious npm packages were published on May 28–29, 2026, across three maintainer aliases and nine organizational scopes. They used internal-looking names and URLs to mimic corporate packages, then executed a postinstall payload that collected host, system, and environment details in reconnaissance-only mode.
The design leaves room for later escalation. If a team mixes private and public sources without pinning package origin, the registry itself becomes the trust boundary, and cleanup after the fact may miss secrets already exposed during install.