mal-2026-14353
Vulnerability from ossf_malicious_packages
Published
2026-08-21 14:29
Modified
2026-08-21 14:49
Summary
Malicious code in @gfe/lx-watcher (npm)
Details

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

Source: amazon-inspector (22abe9bf1ccb266833585bda205a07bc5c9a728763a733aa48b08fe50b640b4e)

All three npm lifecycle hooks (preinstall, install, postinstall) invoke install.js, which POSTs the installer's hostname, OS username, current working directory, timestamp, and hook name to a hardcoded webhook.site collector at https://webhook.site/df384ffa-1094-4bbf-a202-e8b345b3ed18/gfe. The exfiltration fires automatically on npm install with no caller consent and no configuration. The package's main is a no-op createWatcher stub, so a build that resolves this scoped name silently succeeds while host identifiers are leaked. The scoped @gfe/* name combined with the no-op stub and the install-time beacon is the canonical dependency-confusion shape: any organization whose private @gfe/lx-watcher resolves against the public registry leaks host, username, and install-path metadata to the author-controlled collector.

CWE
  • CWE-506 - The product contains code that appears to be malicious in nature.
  • 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"
          },
          {
            "cweId": "CWE-506",
            "description": "The product contains code that appears to be malicious in nature.",
            "name": "Embedded Malicious Code"
          }
        ],
        "indicators": {
          "evidence_files": [
            {
              "path": "install.js",
              "sha256": "5ced5f036a08673dafdc74116a393bdc12de7d9af5308adf0f07859e59e830fb",
              "tlsh": "732175b1c1b5cc513be1a7f0f052490b52b6e323764aa8a0f3ec02192f9c95e02b2989"
            },
            {
              "path": "README.md",
              "sha256": "05a959b5add7f63f428a359aa0993592672cb6b327b6467cc6c33d5bfe2d12b3",
              "tlsh": "2001233c4005e62a3b645760db0bd10000d6c52c913ac5a6d65d6ac60398926b2239e6"
            }
          ],
          "package_integrity": [
            {
              "filename": "lx-watcher-1.5.3.tgz",
              "hashes": {
                "sha1": "1d6e40e1c2b527f5b7346dc8a09ae72471e674cc",
                "sha512_sri": "sha512-je2I2rmDrV1xkhUGKGGA12Yg/KRcKi8GmwSwOyU4DLfJEpVYat+2geFvfyia0RAyfpjhhhx0s+FrkJudmysoAw=="
              }
            }
          ]
        }
      },
      "package": {
        "ecosystem": "npm",
        "name": "@gfe/lx-watcher"
      },
      "versions": [
        "1.5.3",
        "1.5.4"
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "inspector-research@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "id": "IN-MAL-2026-018507",
        "import_time": "2026-08-21T14:47:43.844193878Z",
        "modified_time": "2026-08-21T14:29:13Z",
        "sha256": "1635894d4aed4d98b67666bfe1f849af2884d5c455203d122abe866154a1063b",
        "source": "amazon-inspector",
        "versions": [
          "1.5.3"
        ]
      },
      {
        "id": "IN-MAL-2026-018508",
        "import_time": "2026-08-21T14:47:43.971537029Z",
        "modified_time": "2026-08-21T14:29:24Z",
        "sha256": "22abe9bf1ccb266833585bda205a07bc5c9a728763a733aa48b08fe50b640b4e",
        "source": "amazon-inspector",
        "versions": [
          "1.5.4"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (22abe9bf1ccb266833585bda205a07bc5c9a728763a733aa48b08fe50b640b4e)\nAll three npm lifecycle hooks (preinstall, install, postinstall) invoke install.js, which POSTs the installer\u0027s hostname, OS username, current working directory, timestamp, and hook name to a hardcoded webhook.site collector at https://webhook.site/df384ffa-1094-4bbf-a202-e8b345b3ed18/gfe. The exfiltration fires automatically on `npm install` with no caller consent and no configuration. The package\u0027s `main` is a no-op `createWatcher` stub, so a build that resolves this scoped name silently succeeds while host identifiers are leaked. The scoped `@gfe/*` name combined with the no-op stub and the install-time beacon is the canonical dependency-confusion shape: any organization whose private `@gfe/lx-watcher` resolves against the public registry leaks host, username, and install-path metadata to the author-controlled collector.\n",
  "id": "MAL-2026-14353",
  "modified": "2026-08-21T14:49:31Z",
  "published": "2026-08-21T14:29:13Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/@gfe/lx-watcher/v/1.5.3"
    },
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/@gfe/lx-watcher/v/1.5.4"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in @gfe/lx-watcher (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…