---
id: "MAL-2026-18279"
kind: "package"
aliases: ["MAL-2026-18279"]
title: "Malicious code in @fmr-ap153177/apex-kit-icons (npm)"
severity: "critical"
cvss: null
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "@fmr-ap153177/apex-kit-icons", "fixed": [], "affected": "= 99.9.1", "ecosystem": "npm"}]
ecosystems: ["npm"]
tags: ["malicious", "package"]
not_affected_if: []
published_at: "2026-10-25T15:06:38+00:00"
first_seen_at: "2026-10-26T20:51:52+00:00"
updated_at: "2026-10-26T21:05:48+00:00"
sources: [{"source": "osv-malicious", "url": "https://osv.dev/vulnerability/MAL-2026-18279", "first_seen_at": "2026-10-26T20:51:52+00:00"}]
---

# Malicious code in @fmr-ap153177/apex-kit-icons (npm)

## Affected

- npm:@fmr-ap153177/apex-kit-icons affected = 99.9.1 fixed ?

## Timeline

- 2026-10-26T20:51:52+00:00 osv-malicious https://osv.dev/vulnerability/MAL-2026-18279

## From the sources

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (ff7b14a37bdf740ac9f0e4c8978c2c577d39f04d7b897a5d698cbb220ecf3c9a)
package.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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_
