Malicious Code Injection in senior_tapir-strongdev Package

senior_tapir-strongdev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108533: Malicious code in senior_tapir-strongdev (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The senior_tapir-strongdev package is part of the npm ecosystem, often utilized in various JavaScript projects for its functionalities. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages, aimed at inflating developer reputation scores for token rewards. The presence of such malicious packages poses a significant risk to developers and their projects, as they can lead to unintended consequences and security vulnerabilities.

Vulnerability Detail

The vulnerability in the senior_tapir-strongdev package originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The scripts continuously republish these variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. The ramifications include unauthorized access to sensitive data, disruption of project functionality, and a tarnished reputation for developers using affected packages.

How To Fix

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

npm uninstall senior_tapir-strongdev

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

If an immediate update is not feasible, consider removing the senior_tapir-strongdev package from your project and replacing it with a secure alternative. You can do this by executing the following command: npm uninstall senior_tapir-strongdev. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The senior_tapir-strongdev package has been identified as containing malicious code that poses a significant risk to developers and their projects. It is crucial to take immediate action by updating or removing the package to ensure the security and integrity of your applications.

See every vulnerability recorded for senior_tapir-strongdev →

Share this vulnerability

FAQ

The senior_tapir-strongdev package is an npm package that has been identified as part of a malicious campaign targeting developers for token rewards.

The malicious code can modify your package.json file, remove private flags, and republish variants, potentially compromising your project's integrity and security.

You should immediately update the package to a patched version or uninstall it and replace it with a secure alternative.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

More information can be found in the vulnerability details provided by Amazon Inspector and through the npm registry.

How To Fix

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

npm uninstall senior_tapir-strongdev

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