Malicious Code Injection in sau-naki-up Package
Summary
MAL-2025-165775: Malicious code in sau-naki-up (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 'sau-naki-up' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies its own package.json file and generates numerous variants to pollute the npm registry.
Vulnerability Detail
The vulnerability in the 'sau-naki-up' package originates from its malicious payload, which alters the package.json file by removing private flags, changing version numbers, and creating random package names. This behavior is intended to automate the generation and publication of derivative packages, leading to potential security risks such as reputation damage for developers and pollution of the npm registry with untrustworthy packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sau-naki-upIf 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 'sau-naki-up' package until a fix is released. Additionally, you can monitor your package-lock.json file for any unauthorized changes and revert them if necessary.
Conclusion
The 'sau-naki-up' package has been identified as containing malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to take immediate action by updating or removing the package to mitigate these risks. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for sau-naki-up →
FAQ
The 'sau-naki-up' package is an npm package associated with the tea.xyz token reward campaign, designed to publish derivative packages.
This vulnerability allows the package to modify its own metadata and publish numerous variants, potentially damaging developer reputation and polluting the npm registry.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you cannot update the package, it is advisable to remove it from your project and look for alternative packages that provide similar functionality.
Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, ensuring that you are informed about any potential risks.
