Malicious Code Injection in intan-25 Package: npm Vulnerability Overview

intan-25 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156534: Malicious code in intan-25 (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 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 intan-25 package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in the intan-25 package arises from malicious code that modifies the package.json file by removing private flags and changing 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 security risks, including unauthorized access to sensitive data and the potential for further exploitation of affected systems.

How To Fix

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

npm uninstall intan-25

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 remove the intan-25 package from your project by executing the following command: npm uninstall intan-25. This will prevent the execution of any malicious scripts associated with the package until a fix is applied.

Conclusion

The intan-25 package has been identified as containing malicious code that poses significant risks to projects using it. It is crucial to take immediate action by updating or uninstalling the package to safeguard your application. Utilizing monitoring tools like Vulert can further enhance your project's security posture.

See every vulnerability recorded for intan-25 →

Share this vulnerability

FAQ

The intan-25 package is an npm package associated with the tea.xyz token reward campaign, which has been linked to malicious activities in the npm registry.

The malicious code modifies your package.json file, removes private flags, and can lead to unauthorized republishing of your packages, potentially compromising your project's integrity.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

If you cannot update the package right away, it is advisable to uninstall it as a temporary measure to prevent any malicious activity.

Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review your package.json for any unauthorized changes.

How To Fix

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

npm uninstall intan-25

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