Malicious Code Injection in ilop-9 Package: npm Vulnerability Overview

ilop-9 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156312: Malicious code in ilop-9 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

ilop-9 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. The package is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages. This behavior is linked to the tea.xyz token reward initiative, which incentivizes developers to publish numerous packages, often leading to a polluted registry and potential security risks.

Vulnerability Detail

The vulnerability in the ilop-9 package originates from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This not only inflates developer reputation scores but also compromises the integrity of the npm registry, making it difficult for developers to trust the packages they use. The malicious payload can lead to unintentional use of compromised packages, exposing applications to further vulnerabilities.

How To Fix

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

npm uninstall ilop-9

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 measure, you can avoid using the ilop-9 package and any packages that depend on it. If you have already integrated it into your project, consider replacing it with a reputable alternative that does not exhibit malicious behavior.

Conclusion

The ilop-9 package poses a significant security risk due to its malicious code designed to manipulate npm registry integrity. It is crucial for developers to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for ilop-9 →

Share this vulnerability

FAQ

ilop-9 is an npm package linked to a malicious campaign that aims to manipulate developer reputation scores by flooding the npm registry with derivative packages.

The vulnerability can lead to the use of compromised packages, which may introduce security risks and instability in your application.

You should uninstall the ilop-9 package immediately using the command npm uninstall ilop-9 and check for any dependencies that may be affected.

Yes, consider using established and reputable packages that provide similar functionality without the associated risks of malicious behavior.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

npm uninstall ilop-9

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