Malicious Code Detected in sarumaan_a Package - Version 1.1.1

sarumaan_a Updated 18 Dec 2025

Summary

18/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192606: Malicious code in sarumaan_a (npm). Affects sarumaan_a versions 1.1.1. 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 'sarumaan_a' package is an npm library that is utilized for various functionalities in JavaScript applications. However, version 1.1.1 has been identified as malicious due to its ability to communicate with domains linked to harmful activities and execute commands that may compromise system integrity.

Vulnerability Detail

The vulnerability in the 'sarumaan_a' package arises from its malicious behavior, which includes establishing communication with a domain known for malicious activities and executing harmful commands. This can lead to unauthorized access, data breaches, and potential system compromise, making it a significant threat to any application utilizing this package.

How To Fix

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

npm uninstall sarumaan_a

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, avoid using the 'sarumaan_a' package in your application. If it is already in use, consider replacing it with a similar package that does not exhibit malicious behavior.

Conclusion

The 'sarumaan_a' package version 1.1.1 has been identified as malicious, posing significant risks to applications that utilize it. It is crucial to uninstall this package and monitor for any updates or alternatives to maintain application security.

See every vulnerability recorded for sarumaan_a →

Share this vulnerability

FAQ

The package communicates with a domain associated with malicious activities and executes commands that can compromise system security.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Currently, there is no patched version available for 'sarumaan_a'. It is recommended to uninstall the package.

You should uninstall the package immediately using the command: npm uninstall sarumaan_a.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, ensuring your application remains secure.

How To Fix

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

npm uninstall sarumaan_a

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