Malicious Code Injection in xaver-sasag54-pore: A Threat to npm Packages
Summary
MAL-2025-98525: Malicious code in xaver-sasag54-pore (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 package xaver-sasag54-pore is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, which can inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that alter package metadata.
Vulnerability Detail
The vulnerability in xaver-sasag54-pore arises from malicious code embedded within the package. This code is responsible for modifying the package.json file to remove private flags, changing version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation by attackers. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with similar malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall xaver-sasag54-poreIf 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 prevent the installation of this package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid any inadvertent installations of malicious packages.
Conclusion
The xaver-sasag54-pore package poses a significant risk due to its malicious code designed to manipulate npm packages. It is essential to take immediate action by uninstalling the package and monitoring your project for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for xaver-sasag54-pore →
FAQ
xaver-sasag54-pore is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to unauthorized modifications of your package.json file and may expose your project to further attacks by polluting the npm registry.
You should uninstall the package immediately using 'npm uninstall xaver-sasag54-pore' and check your project for any unauthorized changes.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
