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

intan-79 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156592: Malicious code in intan-79 (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-79 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others in the ecosystem, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to manipulate npm's reputation system through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in the intan-79 package stems from its involvement in a malicious campaign associated with the tea.xyz token reward initiative. This package contains scripts that automatically modify its own package.json file to remove private flags, alter version numbers, and generate random package names, thereby flooding the npm registry with numerous variants. The ramifications of this vulnerability include potential pollution of the npm registry, which can mislead developers and inflate the reputation scores of malicious actors.

How To Fix

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

npm uninstall intan-79

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 intan-79 package and replace it with a trusted alternative. Always verify the integrity and source of packages before including them in your project.

Conclusion

The intan-79 package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating reputation scores. It is essential for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for intan-79 →

Share this vulnerability

FAQ

The intan-79 package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the pollution of the npm registry, making it difficult to find reliable packages and potentially compromising your project's security.

You should uninstall the intan-79 package immediately using the command 'npm uninstall intan-79' and replace it with a trusted alternative.

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

Yes, this vulnerability is part of a broader campaign that may affect multiple packages. It is advisable to review your dependencies regularly.

How To Fix

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

npm uninstall intan-79

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