Vulnerability-Lookup

MAL-2026-16279

Vulnerability from ossf_malicious_packages

Published

2026-09-18 02:57

Modified

2026-09-18 02:57

Summary

Malicious code in xzvbailsx (npm)

Details

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

Source: amazon-inspector (ac9176da252791a96b93c24e702c2245fb96d9655cdf9f31d61e9bc3e0c21528)

package.json declares the dependency libsignal with source github:tenka-san/libsignal-node, an unpinned GitHub ref with no commit SHA, tag, or integrity hash. On npm install, npm fetches whatever HEAD of that repository currently points at and executes any lifecycle scripts (preinstall/install/postinstall) it contains on the installer's machine. The referenced GitHub account is a personal repository unrelated to the WhiskeySockets/Baileys upstream that this package forks. Provenance is further obscured by an identity mismatch: the package is published as xzvbailsx but README/examples describe it as @XzV-RxVz/xbails, and the repository field points to Telegram handles (t.me/JustRxVz, t.me/XzV_ExpzC) rather than a source repository.

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": "package.json",
              "sha256": "2e9a43bc2de0b1b580e4fbe7328188a2134baae3d0dd5e43a83e94c530a647b3",
              "tlsh": "5181ca35ce58ce630ac526e8a9bc0042947559539ec5fc1cb3540bac8f5e15f72b9b3e"
            }
          ],
          "package_integrity": [
            {
              "filename": "xzvbailsx-1.0.0.tgz",
              "hashes": {
                "sha1": "7307380d9e56adfd07bfd2454c225e2a69416011",
                "sha512_sri": "sha512-aBX9cMBN7+Bt+OPTTVDOG0pEXXzZjqLRLcXyrwYonDF7SjvxbyEob7ZqQFu8cIWXj5KWzj0Zdt+X706zC/ZV8Q=="
              }
            }
          ]
        }
      },
      "package": {
        "ecosystem": "npm",
        "name": "xzvbailsx"
      },
      "versions": [
        "1.0.0"
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "inspector-research@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "id": "IN-MAL-2026-020177",
        "import_time": "2026-09-18T03:21:13.660184036Z",
        "modified_time": "2026-09-18T02:57:57Z",
        "sha256": "ac9176da252791a96b93c24e702c2245fb96d9655cdf9f31d61e9bc3e0c21528",
        "source": "amazon-inspector",
        "versions": [
          "1.0.0"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (ac9176da252791a96b93c24e702c2245fb96d9655cdf9f31d61e9bc3e0c21528)\npackage.json declares the dependency `libsignal` with source `github:tenka-san/libsignal-node`, an unpinned GitHub ref with no commit SHA, tag, or integrity hash. On `npm install`, npm fetches whatever HEAD of that repository currently points at and executes any lifecycle scripts (preinstall/install/postinstall) it contains on the installer\u0027s machine. The referenced GitHub account is a personal repository unrelated to the WhiskeySockets/Baileys upstream that this package forks. Provenance is further obscured by an identity mismatch: the package is published as `xzvbailsx` but README/examples describe it as `@XzV-RxVz/xbails`, and the `repository` field points to Telegram handles (`t.me/JustRxVz`, `t.me/XzV_ExpzC`) rather than a source repository.\n",
  "id": "MAL-2026-16279",
  "modified": "2026-09-18T02:57:57Z",
  "published": "2026-09-18T02:57:57Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/xzvbailsx/v/1.0.0"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in xzvbailsx (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