npm registry
Named by 13 kept items in this workspace.
11 items name it under affected products and 2 under tools.
Search every workspace for npm registry. It matches the name as written, so it can find other things that share it.
The items that name it 13
agents reached it directly, bypassing denied-package controls
Package manager ecosystem supported/scanned by vet
platform on which publish-time malware scanning (rolled out July) failed to catch a hash-identical known-malicious payload
Public registry that default npm clients fetch from/publish to; target of self-propagating campaigns publishing trojanized versions via stolen publish tokens.
Platform hosting the malicious packages described
Subject of new publish-time malware scanning announced July 28, 2026; previously scanned every package version post-publish per GitHub's April 2026 post
Hosted the malicious package cluster (lib-mtop, aone-kit, aone-kit-cli, aone-sandbox, local-config-parser, smart-config-manager, cloud-config-fetcher, and 10 top-layer lure packages)
Registry-level account protections discussed: high-impact account cooldown, staged publishing, trusted publishing, 2FA-enforcement policy, postinstall script blocking planned for v12.
publishing metadata (_npmUser field, approver field) and publishing modes: classic, trusted, and staged publishing
package registry whose tooling applied incorrect security-holder metadata to 13 one-character packages
Target of multiple supply chain attacks since September (Shai-Hulud, Chalk/Debug, tea.xyz, axios)
Package registry used for exfiltration via token theft/republishing and supply chain propagation
Nearly 800 (later 1,033 confirmed) malicious packages published delivering RAT/infostealer
All technologies in this workspace.