Malicious Code Injection in intan-51 Package: npm Vulnerability

intan-51 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156562: Malicious code in intan-51 (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-51 package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign aimed at manipulating developer reputation scores through the tea.xyz token reward system. The package is designed to automatically publish derivative versions of itself with altered metadata, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the intan-51 package stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This behavior modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, thereby inflating developer reputation scores fraudulently. The ramifications include potential security risks for developers who unknowingly install these malicious packages, as well as the degradation of the npm registry's integrity.

How To Fix

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

npm uninstall intan-51

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 measure, you can avoid using the intan-51 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies to ensure no malicious packages are included.

Conclusion

The intan-51 package poses a significant risk due to its malicious behavior aimed at manipulating npm's reputation system. It is crucial for developers to be vigilant about their dependencies and to utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove this package and prevent further issues.

See every vulnerability recorded for intan-51 →

Share this vulnerability

FAQ

The intan-51 package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

If your project includes the intan-51 package, it may inadvertently contribute to the pollution of the npm registry and expose your project to security risks.

You should remove the intan-51 package from your project immediately and monitor for any updates or patches that may address this vulnerability.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground at Vulert Scanner without needing to sign up.

The long-term implications include potential security breaches, loss of trust in the npm ecosystem, and the continued proliferation of malicious packages if not addressed promptly.

How To Fix

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

npm uninstall intan-51

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