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

intan-70 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156583: Malicious code in intan-70 (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-70 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 designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to developers and users alike.

Vulnerability Detail

The vulnerability in the intan-70 package originates from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. This behavior can compromise the integrity of the npm ecosystem and potentially expose users to further security risks.

How To Fix

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

npm uninstall intan-70

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 avoid using the intan-70 package and any other packages associated with the tea.xyz token reward campaign. Monitor your package dependencies and remove any suspicious packages that may have been installed inadvertently.

Conclusion

The intan-70 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any malicious packages to safeguard their applications.

See every vulnerability recorded for intan-70 →

Share this vulnerability

FAQ

The intan-70 package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially exposing your application to malicious code and compromising its security.

If you have installed intan-70, you should uninstall it immediately using 'npm uninstall intan-70' and check for any other suspicious packages in your project.

You can use tools like Vulert to monitor your project for open-source vulnerabilities. Vulert uses package-lock.json to provide real-time alerts without requiring code access.

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

How To Fix

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

npm uninstall intan-70

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