Vulnerability-Lookup

MAL-2026-16357

Vulnerability from ossf_malicious_packages

Published

2026-09-21 19:06

Modified

2026-09-21 19:06

Summary

Malicious code in @asdfaskdjfksadhfkasf/nadaver2 (npm)

Details

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

Source: ossf-package-analysis (278821d7a9d245a4193d8536c0b127f61cf1b13335dfe91abaefece6b908a57e)

The OpenSSF Package Analysis project identified '@asdfaskdjfksadhfkasf/nadaver2' @ 102.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Credits

OpenSSF: Package Analysis github.com/ossf/package-analysis openssf.slack.com/channels/package_analysis

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@asdfaskdjfksadhfkasf/nadaver2"
      },
      "versions": [
        "102.0.0"
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "https://github.com/ossf/package-analysis",
        "https://openssf.slack.com/channels/package_analysis"
      ],
      "name": "OpenSSF: Package Analysis",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "import_time": "2026-09-21T19:14:55.95687311Z",
        "modified_time": "2026-09-21T19:06:07Z",
        "sha256": "278821d7a9d245a4193d8536c0b127f61cf1b13335dfe91abaefece6b908a57e",
        "source": "ossf-package-analysis",
        "versions": [
          "102.0.0"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: ossf-package-analysis (278821d7a9d245a4193d8536c0b127f61cf1b13335dfe91abaefece6b908a57e)\nThe OpenSSF Package Analysis project identified \u0027@asdfaskdjfksadhfkasf/nadaver2\u0027 @ 102.0.0 (npm) as malicious.\n\nIt is considered malicious because:\n\n- The package communicates with a domain associated with malicious activity.\n\n- The package executes one or more commands associated with malicious behavior.\n",
  "id": "MAL-2026-16357",
  "modified": "2026-09-21T19:06:07Z",
  "published": "2026-09-21T19:06:07Z",
  "schema_version": "1.7.4",
  "summary": "Malicious code in @asdfaskdjfksadhfkasf/nadaver2 (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