NetSight
kritischMalware-Meldung

GHSA-q32v-qm2p-gw4w

Malicious code in @basis-theory-elements/api-client (npm)

Auswirkung

## Source: amazon-inspector (f84e5b8dd56ced8cdd78e5d5f3b4498111ebcb490cb6e6572674766ab0193dd3) Package @basis-theory-elements/api-client@99.9.1 declares its sole dependency as an HTTPS tarball URL (`"ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-4.0.9.tgz"`) rather than a registry version range. On `npm install`, npm fetches whatever bytes that URL currently serves and runs any lifecycle scripts contained in that tarball, with no version pin, no integrity hash, and no publisher-match check. The shipped index.js is an empty stub, so dependency resolution is the package's entire on-install effect. The package name shadows the `@basis-theory` vendor scope, and the 99.9.1 version is implausibly high for the name — the shape associated with dependency-confusion resolution attacks against internal `@basis-theory-elements/*` packages. --- Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/6306efcd2e5165329b81a44593e5176ac396d59b/osv/malicious/npm/@basis-theory-elements/api-client/MAL-2026-20188.json))

Betroffene Pakete

ÖkosystemPaketBetroffenBehoben in
npm@basis-theory-elements/api-client= 99.9.1nicht erfasst

Schwachstellenklasse

Referenzen