Malicious code in sycm-vendors (npm)
Historical advisory saved 24 Oct 2026 13:17:17 UTC. The publisher may have updated it since then. Latest advisory.
osv · MAL-2026-15523
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b6a876475c44d594b90a19bc6c9bb3d5be6f6d0a19091218ef5e03f92e1b86e1) package.json declares a self-named dependency 'sycm-vendors' whose source is the bare URL https://repo.securityctrl.com/sycm-vendors rather than a registry version range, with no version pin and no integrity hash. On npm install, npm resolves this URL and installs whatever tarball the host returns, executing any lifecycle scripts contained in that tarball. The dependency key equals the package's own name (dependency-confusion shape), and the shipped index.js is an inert stub, so the manifest is the entire payload-delivery mechanism — control of repo.securityctrl.com equates to arbitrary code execution on any installer. ## Source: ghsa-malware (c575a939b8ec452185b6ffb058fdb8a8173a608eb21d1b7c35a6147ab19003aa) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
- Source published
- 28 Aug 2026 23:11:31 UTC
- Source modified
- 29 Aug 2026 18:45:14 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.