Malicious Code Injection in intan-19 Package: npm Vulnerability Overview

intan-19 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156527: Malicious code in intan-19 (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-19 package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often include scripts designed to manipulate package metadata and publish numerous derivative versions, ultimately affecting the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the intan-19 package stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish derivative packages with randomized names. This manipulation removes private flags from package.json, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry. The malicious nature of this package can compromise developer reputation and the overall security of applications relying on it.

How To Fix

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

npm uninstall intan-19

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-19 package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid the installation of this malicious package until a fix is implemented.

Conclusion

The intan-19 package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for intan-19 →

Share this vulnerability

FAQ

The intan-19 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, affecting the integrity of your application's dependencies and potentially compromising security.

You should immediately remove the intan-19 package from your project and update to a secure version if available.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall intan-19

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