Malicious Code Injection in intan-62 Package - npm Vulnerability Summary

intan-62 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156574: Malicious code in intan-62 (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-62 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for rewards. However, it has been compromised to include malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the intan-62 package arises from malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry by continuously republishing variants, which can lead to security risks for developers relying on the integrity of the npm ecosystem. The source of this vulnerability is linked to the tea.xyz token reward campaign, which has been known to flood npm with such malicious packages.

How To Fix

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

npm uninstall intan-62

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-62 package by using npm's package-lock.json file to lock your dependencies. Additionally, you can monitor your project for vulnerabilities using Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The intan-62 package has been identified as containing malicious code that can compromise the integrity of npm packages. It is crucial to remove this package from your dependencies and monitor your project for vulnerabilities using tools like Vulert to ensure ongoing security.

See every vulnerability recorded for intan-62 →

Share this vulnerability

FAQ

The intan-62 package is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies, potentially introducing security risks.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by the intan-62 vulnerability without requiring any signup.

If you cannot update the package due to the absence of a patched version, consider removing it from your project and replacing it with a secure alternative.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software by analyzing the package-lock.json file, providing real-time insights without requiring code access.

How To Fix

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

npm uninstall intan-62

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