mal-2024-1162
Vulnerability from ossf_malicious_packages

Malicious code in hds-input (npm)

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

Source: ossf-package-analysis (331eeefc86867a890820a88481ba976967f613a659320676e1fffee29aa58933)

The OpenSSF Package Analysis project identified 'hds-input' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.



To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "hds-input"
      },
      "versions": [
        "1.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": "2024-04-01T15:33:45.820436455Z",
        "modified_time": "2024-04-01T15:17:59Z",
        "sha256": "331eeefc86867a890820a88481ba976967f613a659320676e1fffee29aa58933",
        "source": "ossf-package-analysis",
        "versions": [
          "1.0.0"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: ossf-package-analysis (331eeefc86867a890820a88481ba976967f613a659320676e1fffee29aa58933)\nThe OpenSSF Package Analysis project identified \u0027hds-input\u0027 @ 1.0.0 (npm) as malicious.\n\nIt is considered malicious because:\n\n- The package communicates with a domain associated with malicious activity.\n",
  "id": "MAL-2024-1162",
  "modified": "2024-04-01T15:17:59Z",
  "published": "2024-04-01T15:17:59Z",
  "schema_version": "1.5.0",
  "summary": "Malicious code in hds-input (npm)"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.