@fmr-ap153177/apex-kit-iconsnpm
Advisory published Updated
@fmr-ap153177/apex-kit-icons is a confirmed malicious npm package (MAL-2026-18279) 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 @fmr-ap153177/apex-kit-icons (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for @fmr-ap153177/apex-kit-icons (version 99.9.1).
If you installed it — respond
Remove @fmr-ap153177/apex-kit-icons 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 @fmr-ap153177/apex-kit-icons 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 @fmr-ap153177/apex-kit-icons-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.