Malicious Code Injection in arif-sambel35-remi: A Threat to npm Packages

arif-sambel35-remi Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99587: Malicious code in arif-sambel35-remi (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 package 'arif-sambel35-remi' is part of a series of npm packages that have been linked to the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious code.

Vulnerability Detail

The vulnerability in 'arif-sambel35-remi' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers who unknowingly integrate these packages into their projects, as well as the degradation of the npm ecosystem.

How To Fix

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

npm uninstall arif-sambel35-remi

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-sambel35-remi' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The 'arif-sambel35-remi' package poses a significant threat due to its malicious code that alters package configurations and repackages software. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert to maintain the integrity of their applications.

See every vulnerability recorded for arif-sambel35-remi →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json files and repackages the software, leading to potential security risks.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

You should uninstall the package immediately using 'npm uninstall arif-sambel35-remi' and look for secure alternatives.

While specific exploits have not been detailed, the modification of package.json can lead to unintentional code execution and security breaches.

Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities, ensuring your software remains secure.

How To Fix

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

npm uninstall arif-sambel35-remi

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