Malicious Code Injection in previous_quokka-gooddev Package
Summary
MAL-2025-107248: Malicious code in previous_quokka-gooddev (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The previous_quokka-gooddev package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This package is particularly vulnerable due to its association with scripts that manipulate package metadata and publish malicious variants.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the previous_quokka-gooddev package, which is linked to the tea.xyz token reward campaign. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as well as damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall previous_quokka-gooddevIf 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 remove the previous_quokka-gooddev package from your project by executing: npm uninstall previous_quokka-gooddev. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The previous_quokka-gooddev package poses a significant security risk due to its malicious code designed to manipulate package metadata and publish harmful variants. It is essential to take immediate action by updating or removing the package to safeguard your project and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for previous_quokka-gooddev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to the injection of malicious code, compromising the security of your project and potentially affecting the integrity of the npm registry.
You should uninstall the previous_quokka-gooddev package immediately and check for any updates or patches that may be available.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
