Malicious Code Detected in ingka-test Package - Security Alert

ingka-test Updated 24 Dec 2025

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192802: Malicious code in ingka-test (npm). Affects ingka-test versions 1.0.0. 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The ingka-test package is an npm library designed for testing purposes within the JavaScript ecosystem. It provides developers with tools to facilitate testing and ensure code quality. However, recent findings have revealed that this package is compromised, potentially exposing users to malicious code that could lead to security breaches.

Vulnerability Detail

The vulnerability in the ingka-test package stems from the inclusion of malicious code, which was identified in version 1.0.0. This code can execute harmful operations on the user's system, potentially leading to data theft, unauthorized access, or other malicious activities. The origin of this vulnerability is linked to a malicious actor who has inserted harmful code into the package, making it imperative for users to take immediate action to protect their systems.

How To Fix

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

npm uninstall ingka-test

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, users are advised to remove the ingka-test package from their projects until a secure version is released. You can do this by executing the following command: npm uninstall ingka-test.

Conclusion

The discovery of malicious code in the ingka-test package poses a significant security risk to users. It is crucial to take immediate action by updating or uninstalling the package to safeguard your systems. Stay informed about updates and utilize tools like Vulert for real-time monitoring of vulnerabilities.

See every vulnerability recorded for ingka-test →

Share this vulnerability

FAQ

The ingka-test package is an npm library used for testing JavaScript applications, providing tools to enhance code quality.

The malicious code can execute harmful operations, potentially leading to data theft or unauthorized access to the user's system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Check your application against this vulnerability using the Vulert playground at Vulert Scanner.

Currently, there is no patched version available. Users should monitor the package repository for updates.

If you cannot update the package, it is recommended to uninstall it until a secure version is released to mitigate risks.

How To Fix

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

npm uninstall ingka-test

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