Malicious Code Injection in arif-tempe54-pore Package: A Threat to npm Users

arif-tempe54-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97594: Malicious code in arif-tempe54-pore (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 arif-tempe54-pore package is part of a broader campaign targeting npm users, specifically associated with the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores. Its functionality is compromised by malicious scripts that alter package metadata, making it a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the arif-tempe54-pore package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants pollutes the npm registry, potentially leading to security risks for developers who inadvertently use these compromised packages. The malicious payload can also affect the reputation of legitimate developers by flooding the registry with low-quality packages.

How To Fix

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

npm uninstall arif-tempe54-pore

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 arif-tempe54-pore package and any packages that depend on it. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to track vulnerabilities in your dependencies.

Conclusion

The arif-tempe54-pore package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata and flood the npm registry. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in your dependencies.

See every vulnerability recorded for arif-tempe54-pore →

Share this vulnerability

FAQ

The arif-tempe54-pore package is a malicious npm package that is part of a campaign to inflate developer reputation scores through automated publishing of derivative packages.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities and a polluted npm registry.

If you have installed the arif-tempe54-pore package, you should uninstall it immediately using 'npm uninstall arif-tempe54-pore' and check your project for any unauthorized changes.

Regularly update your dependencies, monitor your package-lock.json file for changes, and use tools like Vulert to receive real-time alerts for open-source vulnerabilities.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check for vulnerabilities without needing to install anything by using the Vulert playground.

How To Fix

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

npm uninstall arif-tempe54-pore

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