Critical Malicious Code Vulnerability in @ikanngeming/npm Package

@ikanngeming/npm Updated 12 Oct 2026

Summary

12/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17812: Malicious code in @ikanngeming/npm (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 @ikanngeming/npm package is a Node.js library that is typically used for various npm-related functionalities. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to users, as it can lead to unauthorized access and control over the affected systems.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @ikanngeming/npm package. This code can fully compromise any computer that has the package installed, allowing attackers to gain control and access sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to data breaches and unauthorized actions performed on behalf of the user.

How To Fix

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

npm uninstall @ikanngeming/npm

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 workaround, users should ensure that the package is uninstalled and that no remnants of the malicious code remain on the system. This can be done by running the following command: npm uninstall @ikanngeming/npm. However, be aware that simply removing the package may not eliminate all malicious software that has been installed.

Conclusion

The @ikanngeming/npm package contains a critical vulnerability due to embedded malicious code that can compromise systems. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their applications.

See every vulnerability recorded for @ikanngeming/npm →

Share this vulnerability

FAQ

The @ikanngeming/npm package is a Node.js library used for npm-related functionalities, but it has been compromised with malicious code.

If you have the @ikanngeming/npm package installed, your system is likely compromised. It is recommended to remove the package immediately.

You should rotate all secrets and keys stored on the affected computer from a different, secure machine to prevent unauthorized access.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time 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 any signup.

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 @ikanngeming/npm

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