Skip to content
Heist/ feed
Back to feed
Unrated

Malicious code in sc-wizard (npm)

Type: advisorySources: OSV

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b6626c24ff3f61de611b5962b6a1b21a5f694dfb32059e31f956875dc9d1db02) package.json declares the package's only dependency `ltidisafe` as a direct HTTPS tarball URL (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-4.0.1.tgz`) rather than a registry version range. On `npm install`, npm fetches that URL and installs whatever bytes it returns, executing any lifecycle scripts contained in the fetched tarball — unpinned, integrity-unchecked, and outside the npm registry's publish controls. The shipped `index.js` is an empty stub, so the manifest-declared off-registry URL is effectively the entire install-time payload. The dependency source is a mutable third-party storage bucket; whoever controls that URL controls code running on the installer's machine at install time. The high version number (`99.9.1`) relative to a short, generic name is consistent with a dependency-confusion lure intended to win resolution against an internal `sc-wizard` package. ## Source: ossf-package-analysis (54691cc130e614ee031186f7e646c3e6076efad6105a6e9cad68f62aa736516b) The OpenSSF Package Analysis project identified 'sc-wizard' @ 99.9.1 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Products
sc-wizard
Affected versions
99.9.1
Fixed versions
Not specified
CVEs
Not specified
Confirmed fixed CVEs
Not specified
Updated in this feed
1 Nov 2026, 10:11 UTC · Revision 1

Source evidence

Malicious code in sc-wizard (npm)

core-osv · Original source

Published 20 Oct 2026, 03:31 UTC

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b6626c24ff3f61de611b5962b6a1b21a5f694dfb32059e31f956875dc9d1db02) package.json declares the package's only dependency `ltidisafe` as a direct HTTPS tarball URL (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-4.0.1.tgz`) rather than a registry version range. On `npm install`, npm fetches that URL and installs whatever bytes it returns, executing any lifecycle scripts contained in the fetched tarball — unpinned, integrity-unchecked, and outside the npm registry's publish controls. The shipped `index.js` is an empty stub, so the manifest-declared off-registry URL is effectively the entire install-time payload. The dependency source is a mutable third-party storage bucket; whoever controls that URL controls code running on the installer's machine at install time. The high version number (`99.9.1`) relative to a short, generic name is consistent with a dependency-confusion lure intended to win resolution against an internal `sc-wizard` package. ## Source: ossf-package-analysis (54691cc130e614ee031186f7e646c3e6076efad6105a6e9cad68f62aa736516b) The OpenSSF Package Analysis project identified 'sc-wizard' @ 99.9.1 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

osv:MAL-2026-18062

sc-wizard

Fixed versions: Not specified

Complete source record
{
  "id": "c09a61de91c2e5bcaa9438b77ffe3cf90930c761b330a7e97b29b8952e1d5116",
  "url": "https://osv.dev/vulnerability/MAL-2026-18062",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Malicious code in sc-wizard (npm)",
    "summary": "--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b6626c24ff3f61de611b5962b6a1b21a5f694dfb32059e31f956875dc9d1db02) package.json declares the package's only dependency `ltidisafe` as a direct HTTPS tarball URL (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-4.0.1.tgz`) rather than a registry version range. On `npm install`, npm fetches that URL and installs whatever bytes it returns, executing any lifecycle scripts contained in the fetched tarball — unpinned, integrity-unchecked, and outside the npm registry's publish controls. The shipped `index.js` is an empty stub, so the manifest-declared off-registry URL is effectively the entire install-time payload. The dependency source is a mutable third-party storage bucket; whoever controls that URL controls code running on the installer's machine at install time. The high version number (`99.9.1`) relative to a short, generic name is consistent with a dependency-confusion lure intended to win resolution against an internal `sc-wizard` package. ## Source: ossf-package-analysis (54691cc130e614ee031186f7e646c3e6076efad6105a6e9cad68f62aa736516b) The OpenSSF Package Analysis project identified 'sc-wizard' @ 99.9.1 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.",
    "evidence": "osv:MAL-2026-18062",
    "products": [
      {
        "name": {
          "value": "sc-wizard",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [],
        "affected_versions": [
          {
            "value": "99.9.1",
            "evidence": "/affected/0/versions"
          }
        ]
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "MAL-2026-18062",
      "aliases": [
        "MAL-2026-18062"
      ],
      "affected": [
        {
          "package": {
            "name": "sc-wizard",
            "purl": "pkg:npm/sc-wizard",
            "ecosystem": "npm"
          },
          "versions": [
            "99.9.1"
          ],
          "database_specific": {
            "cwes": [
              {
                "name": "Embedded Malicious Code",
                "cweId": "CWE-506",
                "description": "The product contains code that appears to be malicious in nature."
              }
            ],
            "source": "https://github.com/ossf/malicious-packages/blob/main/osv/malicious/npm/sc-wizard/MAL-2026-18062.json",
            "indicators": {
              "evidence_files": [
                {
                  "path": "package.json",
                  "tlsh": "75e0c2204a6166334ec615b6886a555bf3718e5f0418bd1c5adf041c418dbb328fa25c",
                  "sha256": "14ce270c54ef290194a80e17583c917f679b578b2c9ffd952a558d7138f37c09"
                }
              ],
              "package_integrity": [
                {
                  "hashes": {
                    "sha1": "461fa7fb489dfcdae3855c37b84fe50470515535",
                    "sha512_sri": "sha512-Egdobi2KI4YZbdodkno1GjHD2If5Aki8Ysc1qmjfKHFZU+TWO7APNR6vs7BAqUqzrjSIg8KxI5wXn1Kkj/2yIQ=="
                  },
                  "filename": "sc-wizard-99.9.1.tgz"
                }
              ]
            }
          }
        }
      ],
      "modified": "2026-10-25T15:30:04.569290884Z",
      "provider": "osv",
      "references": [
        "https://www.npmjs.com/package/sc-wizard/v/99.9.1"
      ],
      "provider_metadata": {
        "malicious-packages-origins": [
          {
            "sha256": "54691cc130e614ee031186f7e646c3e6076efad6105a6e9cad68f62aa736516b",
            "source": "ossf-package-analysis",
            "versions": [
              "99.9.1"
            ],
            "import_time": "2026-10-20T03:47:10.361366361Z",
            "modified_time": "2026-10-20T03:31:02Z"
          },
          {
            "id": "IN-MAL-2026-021696",
            "sha256": "b6626c24ff3f61de611b5962b6a1b21a5f694dfb32059e31f956875dc9d1db02",
            "source": "amazon-inspector",
            "versions": [
              "99.9.1"
            ],
            "import_time": "2026-10-25T15:15:14.609906356Z",
            "modified_time": "2026-10-25T15:06:25Z"
          }
        ]
      }
    },
    "related_cves": [],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 445636,
  "published_at": "2026-10-20T03:31:02+00:00"
}