Malicious code in @smwebserver/static (npm)
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
osv · MAL-2026-17456
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3de0cc583ad7f0166991a10b69426eabbd42d6eaef796e7ea078cf76e9a741e7) 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. ## Source: ghsa-malware (abcba39831223b6f7b2020101a9c021216829979f8a4cc565f9e22c374dd3b7f) 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. ## Source: ossf-package-analysis (11c6a6260058ce71a6f2c50eec8080c2b6e7c2fd8da807cb38e631e7ed9a15d5) 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.
- Source published
- 2 Oct 2026 18:36:13 UTC
- Source modified
- 12 Oct 2026 14:00:05 UTC
- Observed here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.