mal-2026-14491
Vulnerability from ossf_malicious_packages
Published
2026-08-25 14:10
Modified
2026-08-25 14:10
Summary
Malicious code in chai-as-otc (npm)
Details

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

Source: amazon-inspector (cf771adc4f92ba0d79ea56bdcc1e42db57d1bc7421f0dadb0544f619e16b5ca1)

On module load, lib/initializeCaller.js (required from index.js) runs an IIFE that POSTs the full process.env to a base64-obfuscated endpoint decoding to https://ipcheck-hashed.vercel.app/api/auth/6c1d60d35852ef0c05df, then passes the HTTP response body to new Function("require", response.data) and invokes it with require, yielding arbitrary Node code execution on the installer's host at load time. The package is framed as a pino-style logging middleware with a 'Successfully synced!' cover string, but the actual behavior is a covert credential harvester and remote loader.

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

{
  "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": "lib/initializeCaller.js",
              "sha256": "6ae47651f95735e18c7370aa04d1577ffbd19c20eed57729c777cac6d4a83f4b",
              "tlsh": "9bf08b5d28ba203942ae64e2bf1b14561453f82232d5d865f7cc836a0f8dd4daaa36d8"
            }
          ],
          "package_integrity": [
            {
              "filename": "chai-as-otc-1.0.5.tgz",
              "hashes": {
                "sha1": "7d9f011889a48e4dbee099af2593c725828b8020",
                "sha512_sri": "sha512-yxbmIFpaG/MgpeCu2fX3eUiFT0ok3+gT2OGVYgWSrfwOl/g/L9b0/EwsxKFtjCgYUVN5ctjVxRlDtiatmF02RA=="
              }
            }
          ]
        }
      },
      "package": {
        "ecosystem": "npm",
        "name": "chai-as-otc"
      },
      "versions": [
        "1.0.5"
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "inspector-research@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "id": "IN-MAL-2026-018737",
        "import_time": "2026-08-25T14:21:11.784318666Z",
        "modified_time": "2026-08-25T14:10:16Z",
        "sha256": "cf771adc4f92ba0d79ea56bdcc1e42db57d1bc7421f0dadb0544f619e16b5ca1",
        "source": "amazon-inspector",
        "versions": [
          "1.0.5"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (cf771adc4f92ba0d79ea56bdcc1e42db57d1bc7421f0dadb0544f619e16b5ca1)\nOn module load, lib/initializeCaller.js (required from index.js) runs an IIFE that POSTs the full process.env to a base64-obfuscated endpoint decoding to https://ipcheck-hashed.vercel.app/api/auth/6c1d60d35852ef0c05df, then passes the HTTP response body to new Function(\"require\", response.data) and invokes it with require, yielding arbitrary Node code execution on the installer\u0027s host at load time. The package is framed as a pino-style logging middleware with a \u0027Successfully synced!\u0027 cover string, but the actual behavior is a covert credential harvester and remote loader.\n",
  "id": "MAL-2026-14491",
  "modified": "2026-08-25T14:10:16Z",
  "published": "2026-08-25T14:10:16Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/chai-as-otc/v/1.0.5"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in chai-as-otc (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…

Loading…