Malicious Code Injection in irulkontol Package: npm Vulnerability Summary

irulkontol Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97942: Malicious code in irulkontol (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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The irulkontol package is part of the npm ecosystem, primarily used for various JavaScript applications. It has gained notoriety due to its involvement in the tea.xyz token reward campaign, which has led to the proliferation of malicious packages. This package is designed to inflate developer reputation scores through automated scripts that publish derivative packages with altered metadata.

Vulnerability Detail

The vulnerability in the irulkontol package stems from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for developers to unknowingly install compromised packages, which could lead to data breaches or system vulnerabilities.

How To Fix

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

npm uninstall irulkontol

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, you can avoid using the irulkontol package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity and reputation of packages before installation.

Conclusion

The irulkontol package poses a significant security risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for irulkontol →

Share this vulnerability

FAQ

The irulkontol package is an npm package that has been identified as malicious, primarily involved in the tea.xyz token reward campaign.

The malicious code modifies your project's package.json file, potentially leading to the installation of compromised packages and security vulnerabilities.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

If you have installed the irulkontol package, immediately uninstall it using 'npm uninstall irulkontol' and review your project's dependencies for any other potential vulnerabilities.

Yes, consider using other trusted npm packages that provide similar functionality without the associated risks of malicious code.

How To Fix

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

npm uninstall irulkontol

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