Malicious Code Injection in sanctum-ref-raimu: A Threat to npm Users

sanctum-ref-raimu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165753: Malicious code in sanctum-ref-raimu (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 sanctum-ref-raimu package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to various malicious activities. The primary function of this package is to facilitate token rewards, but it has been compromised to include harmful scripts that can manipulate its own metadata and publish unauthorized variants.

Vulnerability Detail

The vulnerability in the sanctum-ref-raimu package stems from its inclusion in a malicious campaign that employs autopublish scripts to generate and publish derivative packages with randomized names. This manipulation alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, thereby polluting the npm registry. The ramifications include potential security risks for developers who may unknowingly use these compromised packages, leading to reputational damage and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall sanctum-ref-raimu

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 sanctum-ref-raimu package until a fix is released. Additionally, you may consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The sanctum-ref-raimu package has been identified as containing malicious code that poses a significant risk to developers using npm. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for sanctum-ref-raimu →

Share this vulnerability

FAQ

The sanctum-ref-raimu package is an npm package associated with the tea.xyz token reward campaign, which has been compromised to include malicious scripts.

This vulnerability can lead to unauthorized modifications of your package.json file and the potential introduction of malicious code into your project.

If you have installed the sanctum-ref-raimu package, you should update it to the latest version or remove it from your project until a fix is available.

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

More information can be found in the vulnerability report on the GitHub repository or by checking the npm advisory for sanctum-ref-raimu.

How To Fix

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

npm uninstall sanctum-ref-raimu

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