Malicious Code Injection in turisna-spsa-reaf: A Threat to npm Packages

turisna-spsa-reaf Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169357: Malicious code in turisna-spsa-reaf (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'turisna-spsa-reaf' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to a token reward campaign that has been identified as malicious. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names. The vulnerability stems from the package's ability to modify its own metadata and continuously republish variants, leading to potential pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'turisna-spsa-reaf' originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior can lead to the proliferation of malicious packages in the npm registry, which can compromise the integrity of the ecosystem and mislead developers into using potentially harmful software.

How To Fix

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

npm uninstall turisna-spsa-reaf

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 'turisna-spsa-reaf' package from your project by executing 'npm uninstall turisna-spsa-reaf'. This will prevent any malicious scripts from executing until a secure version is available.

Conclusion

The 'turisna-spsa-reaf' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with harmful variants. It is essential to take immediate action by updating or uninstalling the package to safeguard your application. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for turisna-spsa-reaf →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies its own package metadata and republishes variants, potentially flooding the npm registry with harmful packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json. Visit Vulert Scanner to check your application without any signup.

Using this package can lead to the installation of malicious software, compromising your application's security and potentially affecting other dependencies.

Regularly updating your dependencies, using tools like Vulert for monitoring vulnerabilities, and auditing your packages can help prevent similar issues.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

How To Fix

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

npm uninstall turisna-spsa-reaf

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