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

intan-52 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156563: Malicious code in intan-52 (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-52 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign associated with the tea.xyz token reward system. It is designed to manipulate package metadata and inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability in the intan-52 package arises from malicious code that modifies the package.json file to remove private flags and alter version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages, leading to potential security breaches and reputation damage.

How To Fix

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

npm uninstall intan-52

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, avoid using the intan-52 package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like npm audit.

Conclusion

The intan-52 package poses a significant threat to developers using npm due to its malicious code that alters package metadata and republishing behavior. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security and integrity of your applications.

See every vulnerability recorded for intan-52 →

Share this vulnerability

FAQ

The intan-52 package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

The malicious code modifies your package.json file, potentially exposing your project to security risks and affecting the integrity of your npm dependencies.

You should uninstall the intan-52 package immediately using the command npm uninstall intan-52 and check for any dependencies that may be affected.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring access to your code 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.

How To Fix

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

npm uninstall intan-52

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