Malicious Code Injection in intan-43: A Threat to npm Users

intan-43 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156553: Malicious code in intan-43 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package intan-43 is part of a broader campaign associated with the tea.xyz token reward system, which has been flooding the npm ecosystem with malicious packages. These packages are designed to manipulate npm's publishing system, generating derivative packages with random names to artificially inflate developer reputation scores for token rewards. The malicious nature of intan-43 poses significant risks to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in intan-43 originates from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the software supply chain. The malicious payload can affect any project that inadvertently includes this package, leading to reputational damage and security risks.

How To Fix

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

npm uninstall intan-43

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-43 package and any other packages associated with the tea.xyz campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The intan-43 package poses a significant threat to npm users due to its malicious behavior aimed at manipulating the npm registry. It is crucial to remove this package and monitor your dependencies to maintain the integrity of your projects. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities in your software.

See every vulnerability recorded for intan-43 →

Share this vulnerability

FAQ

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

The package modifies your project's package.json file, potentially leading to security vulnerabilities and pollution of the npm registry.

You should uninstall the package immediately using 'npm uninstall intan-43' and review your other dependencies for similar vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall intan-43

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