MAL-2026-18366 (GHSA-R4M9-8735-G966)

Vulnerability from ossf_malicious_packages – Published: 2026-10-29 05:23 – Updated: 2026-10-29 14:15 – Source website
Malicious package
Summary
Malicious code in dsh-redteam-mode (npm)
Affected package
Ecosystem Package Versions
npm dsh-redteam-mode
0.15.2
Details
Amazon Inspector IN-MAL-2026-022059 Reported 2026-10-29 13:43

Package name and shipped file names (score-rules.js, report-replay.js, store-core.js, tools.js, client.js) describe an offensive-security / red-team mode helper. Pattern matches fire on co-occurrence of curl invocations and HTTP GET/POST calls across several library files, which is expected shape for pentest tooling that constructs example requests, replays reports, and scores rules. No lifecycle script-driven install-time execution, no hardcoded exfiltration endpoint, no credential-store or home-directory secret enumeration, and no obfuscated remote fetch were identified in the evidence. The curl and POST tokens appear as part of library methods callers must explicitly invoke rather than install-time or import-time side effects. Offensive-security libraries are a legitimate category and installing them does not by itself attack the installer; however, the breadth of network/command primitives and the lack of traced-code confirmation of their call sites warrants human review.

GitHub Advisory Database GHSA-r4m9-8735-g966 Reported 2026-10-29 05:23

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Indicators
Type Indicator Hashes
Evidence file lib/client.js
sha256 cdce3099d71f3166147fc113643ce28dfa0c527b41b8abfb5a476ed712b0a7a9
tlsh c97419a2e172403a5913d0a5a12ff82fb518640bee026975f9bc76005fce47d9fb96cc
Evidence file lib/report-replay.js
sha256 2730c2492da678c61d0742b752f4b25c6fc3216f825ddb2706badcac330f1c14
tlsh 1332a5e830596151036292f41a1b41f86575da63371b88edf4bc4a892fd58ace2f3fec
Evidence file lib/score-rules.js
sha256 29072348e226aa881f5bab244c7677984ce8480f41af0c959dca76345f452e01
tlsh 02433ab4cea9a4c0122195fd430f5115f518999b616e96a4fefc8e883fcc098cafbd71
Evidence file lib/store-core.js
sha256 04a6c4eee0740e5cb8f3527f2ad1d18cc9a141957584d335d60f335dd67436ab
tlsh 81843ab259f514241303d1b8290f5108f128e917758a98a4ffacd7887fc9578cabebf9
Evidence file lib/tools.js
sha256 31708002ca5975b69621eeebdbcaa04a6a80e1b73fd01d44dce8fee5cf5c3cd8
tlsh 23d307ca29b1f1314ed651a0681b311e7135d28b763628b0fb8d83242f4d6ddd2b6bbc
Package archive dsh-redteam-mode-0.15.2.tgz
sha1 60982a56fe904cd2e3c10e92757c469546ef05d3
sha512_sri sha512-ira5OUGTcmQUfRjs/H6NpITE2oVZgHydvG11f1eEDjPW+pttKaCE+tspaXObyfJon5K6JCbgFMBl5duE2/Ljnw==
CWE
  • CWE-506 - Embedded Malicious Code
Credits
Amazon Inspector inspector-research@amazon.com
References
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"
          },
          {
            "cweId": "CWE-506",
            "description": "The product contains code that appears to be malicious in nature.",
            "name": "Embedded Malicious Code"
          }
        ],
        "indicators": {
          "evidence_files": [
            {
              "path": "lib/client.js",
              "sha256": "cdce3099d71f3166147fc113643ce28dfa0c527b41b8abfb5a476ed712b0a7a9",
              "tlsh": "c97419a2e172403a5913d0a5a12ff82fb518640bee026975f9bc76005fce47d9fb96cc"
            },
            {
              "path": "lib/report-replay.js",
              "sha256": "2730c2492da678c61d0742b752f4b25c6fc3216f825ddb2706badcac330f1c14",
              "tlsh": "1332a5e830596151036292f41a1b41f86575da63371b88edf4bc4a892fd58ace2f3fec"
            },
            {
              "path": "lib/score-rules.js",
              "sha256": "29072348e226aa881f5bab244c7677984ce8480f41af0c959dca76345f452e01",
              "tlsh": "02433ab4cea9a4c0122195fd430f5115f518999b616e96a4fefc8e883fcc098cafbd71"
            },
            {
              "path": "lib/store-core.js",
              "sha256": "04a6c4eee0740e5cb8f3527f2ad1d18cc9a141957584d335d60f335dd67436ab",
              "tlsh": "81843ab259f514241303d1b8290f5108f128e917758a98a4ffacd7887fc9578cabebf9"
            },
            {
              "path": "lib/tools.js",
              "sha256": "31708002ca5975b69621eeebdbcaa04a6a80e1b73fd01d44dce8fee5cf5c3cd8",
              "tlsh": "23d307ca29b1f1314ed651a0681b311e7135d28b763628b0fb8d83242f4d6ddd2b6bbc"
            }
          ],
          "package_integrity": [
            {
              "filename": "dsh-redteam-mode-0.15.2.tgz",
              "hashes": {
                "sha1": "60982a56fe904cd2e3c10e92757c469546ef05d3",
                "sha512_sri": "sha512-ira5OUGTcmQUfRjs/H6NpITE2oVZgHydvG11f1eEDjPW+pttKaCE+tspaXObyfJon5K6JCbgFMBl5duE2/Ljnw=="
              }
            }
          ]
        }
      },
      "package": {
        "ecosystem": "npm",
        "name": "dsh-redteam-mode"
      },
      "versions": [
        "0.15.2"
      ]
    }
  ],
  "aliases": [
    "GHSA-r4m9-8735-g966"
  ],
  "credits": [
    {
      "contact": [
        "inspector-research@amazon.com"
      ],
      "name": "Amazon Inspector",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "malicious-packages-origins": [
      {
        "id": "GHSA-r4m9-8735-g966",
        "import_time": "2026-10-29T06:29:38.362989651Z",
        "modified_time": "2026-10-29T05:23:36Z",
        "sha256": "f8eb264928d14ca579b9ba3317a0dfd42d31091adc475676b63da142c54f44a9",
        "source": "ghsa-malware",
        "versions": [
          "0.15.2"
        ]
      },
      {
        "id": "IN-MAL-2026-022059",
        "import_time": "2026-10-29T14:14:21.933025398Z",
        "modified_time": "2026-10-29T13:43:27Z",
        "sha256": "4b10e8cb5b42b044dde881818592b20e43d2166d6641bd657bf90c2aa5a0c0a2",
        "source": "amazon-inspector",
        "versions": [
          "0.15.2"
        ]
      }
    ]
  },
  "details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (4b10e8cb5b42b044dde881818592b20e43d2166d6641bd657bf90c2aa5a0c0a2)\nPackage name and shipped file names (score-rules.js, report-replay.js, store-core.js, tools.js, client.js) describe an offensive-security / red-team mode helper. Pattern matches fire on co-occurrence of curl invocations and HTTP GET/POST calls across several library files, which is expected shape for pentest tooling that constructs example requests, replays reports, and scores rules. No lifecycle script-driven install-time execution, no hardcoded exfiltration endpoint, no credential-store or home-directory secret enumeration, and no obfuscated remote fetch were identified in the evidence. The curl and POST tokens appear as part of library methods callers must explicitly invoke rather than install-time or import-time side effects. Offensive-security libraries are a legitimate category and installing them does not by itself attack the installer; however, the breadth of network/command primitives and the lack of traced-code confirmation of their call sites warrants human review.\n\n## Source: ghsa-malware (f8eb264928d14ca579b9ba3317a0dfd42d31091adc475676b63da142c54f44a9)\nAny computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.\n",
  "id": "MAL-2026-18366",
  "modified": "2026-10-29T14:15:56.282735404Z",
  "published": "2026-10-29T05:23:36Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-r4m9-8735-g966"
    },
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/dsh-redteam-mode/v/0.15.2"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in dsh-redteam-mode (npm)"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    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.