Malicious Code Vulnerability in stnsxmp3 Package

stnsxmp3 Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1858: Malicious code in stnsxmp3 (npm). Affects stnsxmp3 versions 0.30.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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The stnsxmp3 package is an npm library designed for handling MP3 files, providing functionalities such as encoding, decoding, and manipulation of audio data. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it. Users of this package should be aware of its potential vulnerabilities and take necessary precautions.

Vulnerability Detail

The vulnerability in the stnsxmp3 package stems from the inclusion of malicious code that can compromise the security of applications using it. This code may allow unauthorized access to sensitive data or enable remote code execution, leading to severe ramifications for affected systems. The malicious nature of this code was identified through analysis by security researchers, highlighting the importance of scrutinizing third-party packages.

How To Fix

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

npm uninstall stnsxmp3

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 stnsxmp3 package from your project and replacing it with a safer alternative for MP3 handling. This can be done by executing: npm uninstall stnsxmp3.

Conclusion

The stnsxmp3 package has been identified to contain malicious code, posing significant security risks to applications that utilize it. Users are encouraged to update the package or remove it entirely to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for stnsxmp3 →

Share this vulnerability

FAQ

The stnsxmp3 package is used for encoding, decoding, and manipulating MP3 audio files in JavaScript applications.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to analyze your package-lock.json.

The risks include unauthorized access to sensitive data and potential remote code execution, which can compromise the integrity and security of your application.

Yes, it is advisable to update the stnsxmp3 package to the latest version to mitigate the risks associated with this vulnerability.

If an immediate update is not possible, consider removing the stnsxmp3 package and replacing it with a safer alternative until a secure version is available.

How To Fix

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

npm uninstall stnsxmp3

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