mal-2026-17432
Vulnerability from ossf_malicious_packages
Published
2026-09-30 07:11
Modified
2026-09-30 07:12
Summary
Malicious code in brioche-apl-dev-env (npm)
Details

brioche-apl-dev-env is a dependency-confusion package: it takes a name that looks like an internal project, uses an inflated version (100.0.0) so it outranks private-registry versions, and runs node setup.js || true as a preinstall script on npm install. setup.js sends the hostname, username, working directory, OS, architecture, Node.js version and configured npm registry, with a per-package tracking token, in an HTTPS POST to https://s85r5k14qk.execute-api.us-east-1.amazonaws.com/prod/hook. The npm account amel10 published brioche-apl-dev-env and 9 similar packages within two minutes on 2026-09-30, all with the same setup.js.

CWE
  • CWE-506 - The product contains code that appears to be malicious in nature.
Credits
InvisiRisk, Inc. www.invisirisk.com mailto:research@invisirisk.com
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"
          }
        ]
      },
      "package": {
        "ecosystem": "npm",
        "name": "brioche-apl-dev-env"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "SEMVER"
        }
      ]
    }
  ],
  "credits": [
    {
      "contact": [
        "https://www.invisirisk.com",
        "mailto:research@invisirisk.com"
      ],
      "name": "InvisiRisk, Inc.",
      "type": "FINDER"
    }
  ],
  "database_specific": {
    "iocs": {
      "domains": [
        "s85r5k14qk.execute-api.us-east-1.amazonaws.com"
      ],
      "files": [
        {
          "digests": {
            "sha256": "425187cdaf8ac341e684f3885592d24dbd7f3a74bfdf051910fbb29590992627"
          },
          "note": "preinstall: node setup.js || true",
          "paths": [
            "package.json"
          ],
          "source": "PACKAGE_ARCHIVE"
        },
        {
          "digests": {
            "sha256": "2b68db643189196da35e2b3d16d9e05a3a2df600bc286421932300417c5f0758"
          },
          "note": "Executed by the preinstall script.",
          "paths": [
            "setup.js"
          ],
          "source": "PACKAGE_ARCHIVE"
        }
      ],
      "urls": [
        "https://s85r5k14qk.execute-api.us-east-1.amazonaws.com/prod/hook"
      ]
    }
  },
  "details": "brioche-apl-dev-env is a dependency-confusion package: it takes a name that looks like an internal project, uses an inflated version (100.0.0) so it outranks private-registry versions, and runs `node setup.js || true` as a preinstall script on npm install. setup.js sends the hostname, username, working directory, OS, architecture, Node.js version and configured npm registry, with a per-package tracking token, in an HTTPS POST to `https://s85r5k14qk.execute-api.us-east-1.amazonaws.com/prod/hook`. The npm account amel10 published brioche-apl-dev-env and 9 similar packages within two minutes on 2026-09-30, all with the same setup.js.",
  "id": "MAL-2026-17432",
  "modified": "2026-09-30T07:12:42Z",
  "published": "2026-09-30T07:11:22Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://www.npmjs.com/package/brioche-apl-dev-env"
    }
  ],
  "schema_version": "1.7.4",
  "summary": "Malicious code in brioche-apl-dev-env (npm)"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.



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.