MAL-2026-6294
Vulnerability from ossf_malicious_packages
Published
2026-06-23 14:10
Modified
2026-06-23 14:10
Summary
Malicious code in cue-mcp (npm)
Details

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (5dce71f7cd453bd73a138279dd78ebc607d7c4f6b171bd3b76c7f456a6eb907a)

The package's postinstall.js script runs automatically on npm install and collects host identifying data (os.hostname()) along with process environment variables (process.env), then transmits the data over HTTPS. This shape — system-information harvesting at install time and outbound network transmission via the https module — is a classic install-time exfiltration pattern. There is no legitimate purpose served by reading the installer's environment variables and hostname during postinstall for a package of this kind. Environment variables on developer and CI machines routinely contain credentials (NPM_TOKEN, GITHUB_TOKEN, AWS keys, CI secrets), so this beacon constitutes credential exfiltration risk against any system that installs the package.

CWE
  • CWE-506 - The product contains code that appears to be malicious in nature.
Credits

{
  "affected": [
    {
      "database_specific": {
        "cwes": [
          {
            "cweId": "CWE-506",
            "description": "The product contains code that appears to be malicious in nature.",
            "name": "Embedded Malicious Code"
          }
        ],
        "indicators": {
          "evidence_files": [
            {
              "path": "postinstall.js",
              "sha256": "c92690a6cce612b551d38a96579679de4391e2815d486dcb146d2c2257db6ead",
              "tlsh": "7951d6664a98d2350ba226edf843d4235dbbd05637d698f0b70d52622fc51ac0272bdf"
            }
          ],
          "package_integrity": [
            {
              "filename": "cue-mcp-9999.99.99.tgz",
              "hashes": {
                "sha1": "fc918fa13c4975f4f4408d7230cd921166029645",
                "sha512_sri": "sha512-Y5alvnqilj5ZSJXw3qlS8IsxaZRlwPWnLPJvLpADsDvtngpup75hOMUoLmsj134HbqIMb18lL409vQBtS+2F5w=="
              }
            }
          ]
        }
      },
      "package": {
        "ecosystem": "npm",
        "name": "cue-mcp"
      },
      "versions": [
        "9999.99.99"
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "inspector-research@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "id": "IN-MAL-2026-007199",
        "import_time": "2026-06-23T14:23:02.623475392Z",
        "modified_time": "2026-06-23T14:10:26Z",
        "sha256": "5dce71f7cd453bd73a138279dd78ebc607d7c4f6b171bd3b76c7f456a6eb907a",
        "source": "amazon-inspector",
        "versions": [
          "9999.99.99"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (5dce71f7cd453bd73a138279dd78ebc607d7c4f6b171bd3b76c7f456a6eb907a)\nThe package\u0027s postinstall.js script runs automatically on `npm install` and collects host identifying data (os.hostname()) along with process environment variables (process.env), then transmits the data over HTTPS. This shape \u2014 system-information harvesting at install time and outbound network transmission via the `https` module \u2014 is a classic install-time exfiltration pattern. There is no legitimate purpose served by reading the installer\u0027s environment variables and hostname during postinstall for a package of this kind. Environment variables on developer and CI machines routinely contain credentials (NPM_TOKEN, GITHUB_TOKEN, AWS keys, CI secrets), so this beacon constitutes credential exfiltration risk against any system that installs the package.\n",
  "id": "MAL-2026-6294",
  "modified": "2026-06-23T14:10:26Z",
  "published": "2026-06-23T14:10:26Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/cue-mcp/v/9999.99.99"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in cue-mcp (npm)"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…