Malicious code in @basis-theory-elements/api-client (npm)
MAL-2026-20188 · GHSA-94wh-c496-hm43
Published · Modified
Dependency scanning
Check whether @basis-theory-elements/api-client is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
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.
Source: ghsa-malware (f5184871c5335799fd89bbfa052c3975c90631140b0f4b2864b0fd8af6e07849)
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.
Ready to move
Start Securing
Free, no credit card | First findings in minutes