Malicious npm packages abuse dependency confusion to profile developer environments
2026-06-02T08:52:18Z•442d43118b3d0add5137c78db83828191d109dd9ef5308af99c8321d32858290
CI/CDMicrosoft Threat Intelligencebuild systemsdependency confusiondetectiondeveloper environmentsmalicious packagesmitigationnpmreconnaissancesoftware supply chain
What happened
Microsoft Threat Intelligence documented a dependency‑confusion supply‑chain campaign that published 33 malicious npm packages to the public registry. The packages were designed to be pulled into developer and CI/build environments (via name collisions with internal packages) and executed during npm install to gather reconnaissance information about developer machines and build systems. Observed tradecraft included environment and workspace profiling to identify credentials, tooling, and CI contexts; the report details the attack chain, detection signals, and mitigation opportunities to help组织
Why it matters
A reviewed impact interpretation has not been published for this record.
Evidence and limitations
- Source ID
- microsoft_security_blog
- Record identifier
- 442d43118b3d0add5137c78db83828191d109dd9ef5308af99c8321d32858290
- Enrichment time
- 2026-06-02T08:52:18Z
- AI-assisted enrichment
- Yes
This record may overlap with other records. Its enrichment can be incomplete or wrong, and machine assistance was used. Validate consequential decisions against the linked source and your own environment.