-= Per source details. Do not edit below this line.=-
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.
{
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-019068",
"source": "amazon-inspector",
"import_time": "2026-08-28T23:14:35.889650978Z",
"modified_time": "2026-08-28T23:11:31Z",
"sha256": "b6a876475c44d594b90a19bc6c9bb3d5be6f6d0a19091218ef5e03f92e1b86e1",
"versions": [
"55.0.0"
]
}
]
}[
{
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code",
"cweId": "CWE-506"
}
]
{
"package_integrity": [
{
"filename": "sycm-vendors-55.0.0.tgz",
"hashes": {
"sha512_sri": "sha512-25lugCFOcUp6nGzNfuSHXWM1ZHbyeGZbgJB+wBuJK3LhFUGinOsZOLnxvQ4S6ZXlBqZJJNpSMetoLuhiZYRL6A==",
"sha1": "699ad610dff53557e935249118b67b6437927c5e"
}
}
],
"evidence_files": [
{
"path": "package.json",
"tlsh": "54e0c2244a11a2b30dca625f88bdc45773158e5b14147c8992eb051c818d9b36afe35c",
"sha256": "99f09fc1e47dc34f3c18f53edb28509c3323476661304ead7ca2e877e82f2b9a"
}
]
}
"https://github.com/ossf/malicious-packages/blob/main/osv/malicious/npm/sycm-vendors/MAL-2026-15523.json"