sycm-vendors

Details

**Severity:** Critical

**Affected versions:** `= 55.0.0`

## 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.

---

Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/8278ab2bd67eee704962fa11801bbf9da85d4939/osv/malicious/npm/sycm-vendors/MAL-2026-15523.json))

**References:**
- https://github.com/ossf/malicious-packages/blob/8278ab2bd67eee704962fa11801bbf9da85d4939/osv/malicious/npm/sycm-vendors/MAL-2026-15523.json
- https://www.npmjs.com/package/sycm-vendors/v/55.0.0
- https://github.com/advisories/GHSA-949x-vj77-3wv6

Compromised versions (1)

• = 55.0.0

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.