Malicious Code Detected in ikst Package - Security Alert

ikst Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-23045: Malicious code in ikst (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The ikst package is an npm library designed for various functionalities within JavaScript applications. It is utilized by developers for its ease of integration and lightweight nature. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that rely on it.

Vulnerability Detail

The vulnerability in the ikst package stems from the inclusion of malicious code that can compromise the integrity of applications using it. This code can lead to unauthorized access, data breaches, and potential exploitation of the system. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall ikst

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, consider removing the ikst package from your project until a secure version is released. You can do this by running the command: 'npm uninstall ikst'. This will help prevent any potential exploitation while you await a fix.

Conclusion

The discovery of malicious code in the ikst package poses a serious threat to applications utilizing it. Users are urged to take immediate action by updating or uninstalling the package to protect their systems. Monitoring tools like Vulert can assist in identifying vulnerabilities in your projects.

See every vulnerability recorded for ikst →

Share this vulnerability

FAQ

The ikst package is an npm library used in JavaScript applications for various functionalities, but it has recently been found to contain malicious code.

The malicious code can lead to unauthorized access and data breaches, compromising the security of your application.

You should immediately update or uninstall the ikst package to mitigate the risks associated with the malicious code.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Related vulnerabilities

Recent vulnerabilities recorded for ikst.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall ikst

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback