Malicious Code Injection in final-scale-static-yaml-debug Package
Summary
MAL-2025-186980: Malicious code in final-scale-static-yaml-debug (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The final-scale-static-yaml-debug package is part of the npm ecosystem, typically used for handling YAML files in JavaScript applications. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages. The vulnerability arises from the package's design, which allows for the automatic generation and publication of variants that can pollute the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the final-scale-static-yaml-debug package, which is linked to the tea.xyz token reward campaign. It includes scripts that modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the proliferation of unwanted packages in the npm registry, potentially compromising the integrity of applications that depend on this ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall final-scale-static-yaml-debugIf 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 workaround, consider using alternative packages that provide similar functionality without the associated risks. Always verify the source and reputation of packages before including them in your project.
Conclusion
The final-scale-static-yaml-debug package poses a significant risk due to its malicious code that can compromise npm registry integrity. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain application security.
See every vulnerability recorded for final-scale-static-yaml-debug →
FAQ
It is an npm package used for handling YAML files, but it has been compromised and is part of a malicious campaign.
The vulnerability can lead to the introduction of unwanted packages in your application, potentially compromising its security and stability.
You should uninstall the package immediately and check for any alternative packages that are safe to use.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without signing up.
