MAL-2026-17415
Vulnerability from ossf_malicious_packages
Published
2026-09-30 13:50
Modified
2026-09-30 13:50
Summary
Malicious code in com.epi.e2e_test (npm)
Details

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

Source: amazon-inspector (5a0c1068af335818f2b9d905f2d39ebe594f84a6c63e470877692554bc95103b)

package.json declares a preinstall script that runs index.js on npm install. index.js collects host identifiers (os.homedir(), os.hostname(), os.userInfo().username, dns.getServers(), current working directory) along with the contents of the package.json and POSTs them over HTTPS to the hardcoded external host meta.brs.cx. This behavior fires automatically on install with no user interaction, and the collected data is characteristic of dependency-confusion / internal-name reconnaissance beacons used to identify targets for follow-on attacks.

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

{
  "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": "6997cc0dbb734648576645638c3354b176fdd0f7ad89055626d752474a96237c",
              "tlsh": "c711c0e4c1e123600dba55c47899d00816aad737780e6cd8f68d03d04fceabc70b2af1"
            }
          ],
          "package_integrity": [
            {
              "filename": "com.epi.e2e_test-1.2.2.tgz",
              "hashes": {
                "sha1": "1915501cc527d33f0e9248146554cd01cc2d7311",
                "sha512_sri": "sha512-HMkc/9uIkxiPGGLJGjhx0pREJCPWQ4U9zyvTX8tWENoiQN7Ui1nHVxDAKB7cYH13dv6uWHWxPFa4ALQwltl0nA=="
              }
            }
          ]
        }
      },
      "package": {
        "ecosystem": "npm",
        "name": "com.epi.e2e_test"
      },
      "versions": [
        "1.2.2"
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "inspector-research@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "id": "IN-MAL-2026-020822",
        "import_time": "2026-09-30T14:21:25.191390953Z",
        "modified_time": "2026-09-30T13:50:32Z",
        "sha256": "5a0c1068af335818f2b9d905f2d39ebe594f84a6c63e470877692554bc95103b",
        "source": "amazon-inspector",
        "versions": [
          "1.2.2"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (5a0c1068af335818f2b9d905f2d39ebe594f84a6c63e470877692554bc95103b)\npackage.json declares a preinstall script that runs index.js on npm install. index.js collects host identifiers (os.homedir(), os.hostname(), os.userInfo().username, dns.getServers(), current working directory) along with the contents of the package.json and POSTs them over HTTPS to the hardcoded external host meta.brs.cx. This behavior fires automatically on install with no user interaction, and the collected data is characteristic of dependency-confusion / internal-name reconnaissance beacons used to identify targets for follow-on attacks.\n",
  "id": "MAL-2026-17415",
  "modified": "2026-09-30T13:50:32Z",
  "published": "2026-09-30T13:50:32Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/com.epi.e2e_test/v/1.2.2"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in com.epi.e2e_test (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…

Loading…

Loading…

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.


Loading…