Malicious Code Injection in intan-26 Package: A Threat to npm Ecosystem

intan-26 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156535: Malicious code in intan-26 (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-26 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package 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 that automate the creation and publication of derivative packages, potentially compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the intan-26 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 not only inflates developer reputation scores for token rewards but also poses significant risks to users who may unknowingly install these compromised packages.

How To Fix

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

npm uninstall intan-26

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, avoid using the intan-26 package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to identify and remove any malicious or untrusted packages.

Conclusion

The intan-26 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with compromised packages. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for intan-26 →

Share this vulnerability

FAQ

The intan-26 package is an npm package associated with a token reward campaign that has been identified as containing malicious code.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities and pollution of the npm registry.

You should uninstall the intan-26 package immediately using 'npm uninstall intan-26' and audit your project for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground without any signup.

Yes, consider using other reputable packages that provide similar functionality without the risks associated with intan-26.

How To Fix

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

npm uninstall intan-26

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