{"id":"MAL-2026-18279","revision":"acfddd3372954de6aa2769b7fd83917f","records":[{"revision":"acfddd3372954de6aa2769b7fd83917f","observedAt":"2026-10-25T16:17:16.268+00:00","statement":{"source":"osv","id":"MAL-2026-18279","aliases":[],"title":"Malicious code in @fmr-ap153177/apex-kit-icons (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (ff7b14a37bdf740ac9f0e4c8978c2c577d39f04d7b897a5d698cbb220ecf3c9a)\npackage.json declares the sole dependency `ltidisafe` as a direct HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.9.1.tgz) instead of a registry version range. On `npm install`, npm fetches that URL and installs whatever bytes it returns, running any lifecycle scripts contained in the fetched tarball, with no version pin and no integrity check. The shipped `index.js` is an empty stub, so dependency resolution from this off-registry source is the entire install-time effect of the package. Control of that storage bucket equates to code execution on any machine that installs this package. The scoped name resembling an internal/kit package (`@fmr-ap153177/apex-kit-icons`) at an implausibly high version (99.9.1) is consistent with a dependency-confusion lure shape.\n","state":0,"publishedAt":"2026-10-25T15:06:38+00:00","modifiedAt":"2026-10-25T15:30:05.5609786+00:00","affected":[{"ecosystem":"npm","name":"@fmr-ap153177/apex-kit-icons","ranges":[],"versions":["99.9.1"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/@fmr-ap153177/apex-kit-icons/v/99.9.1"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-18279","license":"OSV · upstream source license applies","key":"osv:MAL-2026-18279","identifiers":["MAL-2026-18279"]},"retained":false,"historicalAffected":[]}],"coverage":[]}