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

intan-5 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156560: Malicious code in intan-5 (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 intan-5 package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign associated with the tea.xyz token reward system. This campaign has led to the proliferation of packages that manipulate the npm registry, potentially compromising the integrity of projects that depend on this package.

Vulnerability Detail

The vulnerability in the intan-5 package stems from its involvement in a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically generate and publish new packages with altered metadata, including the removal of private flags and randomization of package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, leading to potential security risks for developers who may unknowingly integrate these malicious packages into their projects.

How To Fix

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

npm uninstall intan-5

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 prevent the installation of the intan-5 package by using the following command: npm uninstall intan-5. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to alert you of any open-source vulnerabilities in real-time.

Conclusion

The intan-5 package poses a significant security risk due to its involvement in a malicious npm campaign. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the package, and utilize tools like Vulert to monitor their projects for any potential threats.

See every vulnerability recorded for intan-5 →

Share this vulnerability

FAQ

The intan-5 package is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.

You should uninstall the intan-5 package immediately and check for any updates or patches. Consider using alternative packages that are secure.

You can use Vulert to monitor your project for vulnerabilities by analyzing your package-lock.json file. This tool provides real-time alerts for any open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall intan-5

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