@smwebserver/staticnpm
Advisory published Updated
@smwebserver/static is a confirmed malicious npm package (MAL-2026-17456) 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 @smwebserver/static (npm)
What this malware does
The package ships an effectively empty index.js and its only real content is a manifest-level dependency sourced from an arbitrary HTTPS URL rather than a registry version range: dependencies.ltidisafe is set to https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.7.9.tgz. On npm install, npm fetches that tarball and installs it, running any lifecycle scripts it contains, with no version pin, no integrity hash, and no signature check. The bucket host is not a publisher-controlled domain tied to this package, and the contents at that URL can be swapped at any time by whoever owns the bucket. The absence of lifecycle scripts in this package's own package.json does not mitigate the issue, because the fetched tarball's scripts are what execute. Installing this package therefore delegates full install-time code execution on the installer's machine to a mutable, off-registry source.
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.
The OpenSSF Package Analysis project identified '@smwebserver/static' @ 99.9.1 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for @smwebserver/static (version 99.9.1).
If you installed it — respond
Remove @smwebserver/static 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 @smwebserver/static 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
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks @smwebserver/static-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.