mal-0000-ossf-package-analysis-3a35642da2386734
Vulnerability from ossf_malicious_packages
Published
2026-01-15 06:35
Modified
2026-01-15 06:35
Summary
Malicious code in admin1001 (npm)
Details

The OpenSSF Package Analysis project identified 'admin1001' @ 4.4.3 (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.


{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "admin1001"
      },
      "versions": [
        "4.4.3"
      ]
    }
  ],
  "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-01-15T06:46:44.201158424Z",
        "modified_time": "2026-01-15T06:35:30Z",
        "sha256": "3a35642da2386734190f5408d1837445336dddbb1b4dc32accc25346e8b63e8e",
        "source": "ossf-package-analysis",
        "versions": [
          "4.4.3"
        ]
      }
    ]
  },
  "details": "The OpenSSF Package Analysis project identified \u0027admin1001\u0027 @ 4.4.3 (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": "",
  "modified": "2026-01-15T06:35:30Z",
  "published": "2026-01-15T06:35:30Z",
  "schema_version": "1.7.4",
  "summary": "Malicious code in admin1001 (npm)"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…