Malicious Code Injection in operational_sturgeon_z3n: A Threat to npm Packages
Summary
MAL-2025-106746: Malicious code in operational_sturgeon_z3n (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 'operational_sturgeon_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised due to its malicious intent, leading to potential risks for developers and users relying on npm packages.
Vulnerability Detail
The vulnerability in 'operational_sturgeon_z3n' originates from its design to include malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names to flood the npm registry with derivative packages. This behavior not only pollutes the registry but also poses a risk of reputation damage to legitimate developers and can lead to the unintentional use of compromised packages in applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall operational_sturgeon_z3nIf 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 malicious package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include 'operational_sturgeon_z3n' in its dependencies. You can also use the following command to audit your project for vulnerabilities: npm audit.
Conclusion
The 'operational_sturgeon_z3n' package poses a significant threat due to its malicious code designed to manipulate npm packages. It is crucial for developers to be vigilant and remove such packages from their projects to maintain security and integrity. Utilizing tools like Vulert can aid in monitoring and identifying vulnerabilities effectively.
See every vulnerability recorded for operational_sturgeon_z3n →
FAQ
'operational_sturgeon_z3n' is an npm package that has been identified as malicious, associated with a campaign to inflate developer reputation scores.
The vulnerability can lead to the unintentional use of compromised packages, potentially exposing your project to security risks and damaging your reputation as a developer.
You should immediately remove 'operational_sturgeon_z3n' from your project and check for any updates or patches that may address the vulnerability.
Yes, you can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
