Malicious Code Injection in ill_salamander_requirement Package

ill_salamander_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94921: Malicious code in ill_salamander_requirement (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The ill_salamander_requirement 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 that aims to exploit the npm registry by flooding it with derivative packages. The primary function of this package is to facilitate the tea.xyz token reward campaign, which incentivizes developers to publish numerous packages to inflate their reputation scores.

Vulnerability Detail

The vulnerability in the ill_salamander_requirement package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The malicious payload is designed to execute autopublish scripts that automate the creation and publication of these harmful packages, posing a significant risk to developers and users relying on the npm registry.

How To Fix

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

npm uninstall ill_salamander_requirement

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 remove the ill_salamander_requirement package from your project by executing the following command: npm uninstall ill_salamander_requirement. This will prevent any malicious code from executing until a patched version is available.

Conclusion

The ill_salamander_requirement package poses a significant risk due to its malicious behavior of modifying package files and republishing harmful variants. It is essential to take immediate action by updating or removing the package and utilizing monitoring tools like Vulert to safeguard your projects from future vulnerabilities.

See every vulnerability recorded for ill_salamander_requirement →

Share this vulnerability

FAQ

The ill_salamander_requirement package is an npm package associated with a token reward campaign that has been identified as malicious.

This vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing malicious code.

If you have installed the ill_salamander_requirement package, it is recommended to uninstall it immediately and monitor for any updates or patches.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

To prevent similar vulnerabilities, regularly update your dependencies, use tools like Vulert for monitoring, and review package sources before installation.

How To Fix

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

npm uninstall ill_salamander_requirement

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