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

intan-81 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156595: Malicious code in intan-81 (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

The intan-81 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. The primary function of such packages is to manipulate the npm registry by creating and publishing derivative packages, thereby inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the intan-81 package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation by malicious actors. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs these tactics to manipulate the npm ecosystem.

How To Fix

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

npm uninstall intan-81

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 workaround, you can temporarily avoid using the intan-81 package by removing it from your dependencies. Additionally, you can monitor your project's package-lock.json file for any unauthorized changes or additions.

Conclusion

The intan-81 package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata and floods the registry with unauthorized variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security.

See every vulnerability recorded for intan-81 →

Share this vulnerability

FAQ

The intan-81 package is an npm package associated with a token reward campaign that has been found to contain malicious code.

The malicious code modifies your package.json file, removes private flags, and publishes unauthorized variants, potentially leading to security vulnerabilities.

You should remove the intan-81 package from your project immediately and monitor your package-lock.json for any changes.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without signing up.

Regularly audit your dependencies, use tools like Vulert to monitor vulnerabilities, and ensure you are using trusted packages from reputable sources.

How To Fix

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

npm uninstall intan-81

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