MAL-2026-18049 (GHSA-3XPJ-MFQG-V52M)

Vulnerability from ossf_malicious_packages – Published: 2026-10-19 22:19 – Updated: 2026-10-20 18:28 – Source website
Malicious package
Summary
Malicious code in @an1mshnpmb9c84920/pipe-dns-m19t2 (npm)
Affected package
Ecosystem Package Versions
npm @an1mshnpmb9c84920/pipe-dns-m19t2
Affected: All versions (semver)
1.0.0
Details
Amazon Inspector IN-MAL-2026-021528 Reported 2026-10-20 18:16

The package's prepare lifecycle script executes index.js, which builds a subdomain string from the installer's hostname and the npm lifecycle event name and issues a dns.lookup against npmexec19t2--768.oob.awss.dev, an authoritative zone controlled by the publisher. This leaks installer identity to an external party automatically on npm install via an out-of-band DNS channel. The package.json repository field points at a sibling host on the same oob.awss.dev infrastructure, and the README contains only the word 'owned', with no legitimate functionality shipped in the tarball.

GitHub Advisory Database GHSA-3xpj-mfqg-v52m Reported 2026-10-19 22:19

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Indicators
Type Indicator Hashes
Evidence file index.js
sha256 debea698d09b4c543311cd711e78409a22952bf488fe3d56c266e942553d937d
tlsh 68d0959fd2501b8632005548d35c12005df7cfd11240d5c4b406dcc3146516d0763ff5
Evidence file package.json
sha256 be6ceece6ad6da08110d6dab0d6baa38816c9cd65e1bb66598c02d5b58f2aa40
tlsh 4cd02b684e60ec732a100982a677dc88606700b706d4564408535e5c82fb5d5e01e34d
CWE
  • CWE-506 - Embedded Malicious Code
Credits
Amazon Inspector inspector-research@amazon.com

{
  "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": "index.js",
              "sha256": "debea698d09b4c543311cd711e78409a22952bf488fe3d56c266e942553d937d",
              "tlsh": "68d0959fd2501b8632005548d35c12005df7cfd11240d5c4b406dcc3146516d0763ff5"
            },
            {
              "path": "package.json",
              "sha256": "be6ceece6ad6da08110d6dab0d6baa38816c9cd65e1bb66598c02d5b58f2aa40",
              "tlsh": "4cd02b684e60ec732a100982a677dc88606700b706d4564408535e5c82fb5d5e01e34d"
            }
          ]
        }
      },
      "package": {
        "ecosystem": "npm",
        "name": "@an1mshnpmb9c84920/pipe-dns-m19t2"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": [
        "1.0.0"
      ]
    }
  ],
  "aliases": [
    "GHSA-3xpj-mfqg-v52m"
  ],
  "credits": [
    {
      "contact": [
        "inspector-research@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "id": "GHSA-3xpj-mfqg-v52m",
        "import_time": "2026-10-19T22:24:25.280570267Z",
        "modified_time": "2026-10-19T22:19:38Z",
        "ranges": [
          {
            "events": [
              {
                "introduced": "0"
              }
            ],
            "type": "SEMVER"
          }
        ],
        "sha256": "0af2574cde6941a12e82bbc6fb4de1d1fd75b2434ab5e88dbebc4e8ea644bd36",
        "source": "ghsa-malware"
      },
      {
        "id": "IN-MAL-2026-021528",
        "import_time": "2026-10-20T18:22:19.298454577Z",
        "modified_time": "2026-10-20T18:16:15Z",
        "sha256": "548a4b4d6c63df4cc62bd7e753758dc32f98b3ed9adb7fbee204493838614eea",
        "source": "amazon-inspector",
        "versions": [
          "1.0.0"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (548a4b4d6c63df4cc62bd7e753758dc32f98b3ed9adb7fbee204493838614eea)\nThe package\u0027s prepare lifecycle script executes index.js, which builds a subdomain string from the installer\u0027s hostname and the npm lifecycle event name and issues a dns.lookup against npmexec19t2--768.oob.awss.dev, an authoritative zone controlled by the publisher. This leaks installer identity to an external party automatically on npm install via an out-of-band DNS channel. The package.json repository field points at a sibling host on the same oob.awss.dev infrastructure, and the README contains only the word \u0027owned\u0027, with no legitimate functionality shipped in the tarball.\n\n## Source: ghsa-malware (0af2574cde6941a12e82bbc6fb4de1d1fd75b2434ab5e88dbebc4e8ea644bd36)\nAny computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.\n",
  "id": "MAL-2026-18049",
  "modified": "2026-10-20T18:28:04.921219512Z",
  "published": "2026-10-19T22:19:38Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-3xpj-mfqg-v52m"
    },
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/@an1mshnpmb9c84920/pipe-dns-m19t2/v/1.0.0"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in @an1mshnpmb9c84920/pipe-dns-m19t2 (npm)"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.