Malicious Code Injection in safe_quokka-appteadev Package
Summary
MAL-2025-108334: Malicious code in safe_quokka-appteadev (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 safe_quokka-appteadev package is part of the npm ecosystem, typically used for various development purposes. However, it has been identified as part of a malicious campaign that aims to exploit npm's package management system. This package, like others in the campaign, contains scripts designed to manipulate package metadata and inflate developer reputation scores through the generation of numerous derivative packages.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign associated with the tea.xyz token reward initiative. It includes scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of projects relying on this package. The malicious payload can potentially allow unauthorized access to sensitive information or disrupt the functionality of dependent applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall safe_quokka-appteadevIf 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 using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include the safe_quokka-appteadev package and regularly audit your dependencies for any malicious packages.
Conclusion
The safe_quokka-appteadev package has been identified as a vector for malicious code injection, posing significant risks to applications that utilize it. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.
See every vulnerability recorded for safe_quokka-appteadev →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
The risks include unauthorized access to sensitive information, disruption of application functionality, and pollution of the npm registry.
You can remove the package by running 'npm uninstall safe_quokka-appteadev' in your terminal.
Regularly audit your dependencies and use tools like Vulert to monitor for open-source vulnerabilities in real-time.
