@futurae-public/adaptive-jsnpm
Advisory published Updated
@futurae-public/adaptive-js is a confirmed malicious npm package (MAL-2026-18280) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @futurae-public/adaptive-js (npm)
What this malware does
package.json declares its sole dependency ltidisafe as a direct HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.9.2.tgz) rather than a registry version range. On npm install, npm fetches that tarball with no version pin, no integrity hash, and no registry provenance, then installs it and runs any lifecycle scripts it contains on the installer's machine. The shipped index.js is an inert stub (exports {}), so the manifest's off-registry fetch is the only functional effect of installing this package. The dependency host is unrelated to the publishing scope @futurae-public, and the implausibly high version (99.9.1) is consistent with a dependency-confusion shape intended to win resolution over an internal package of the same name. Whoever controls the tarball URL controls code executed on every installer.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for @futurae-public/adaptive-js (version 99.9.1).
If you installed it — respond
Remove @futurae-public/adaptive-js from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @futurae-public/adaptive-js was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @futurae-public/adaptive-js-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.