Malicious Code Injection in dewikartika Package: A Threat to npm Users
Summary
MAL-2025-171108: Malicious code in dewikartika (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 dewikartika package is part of the npm ecosystem, often utilized in various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages flooding the npm registry. This package, like others in the campaign, is designed to manipulate npm's publishing mechanisms, potentially compromising the integrity of applications that depend on it.
Vulnerability Detail
The vulnerability in the dewikartika package stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only inflates developer reputation scores for token rewards but also poses significant risks to users by introducing untrusted code into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dewikartikaIf 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 dewikartika package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks from malicious packages.
Conclusion
The dewikartika package poses a significant threat to npm users due to its malicious code that alters package metadata and repackages itself with random names. Immediate action is required to remove this package and safeguard your applications from potential risks. Regular monitoring and auditing of dependencies are essential to maintain security.
See every vulnerability recorded for dewikartika →
FAQ
Dewikartika is an npm package that has been identified as part of a malicious campaign aimed at manipulating npm's publishing system.
The vulnerability can introduce untrusted code into your application, potentially leading to security breaches and compromised data integrity.
You should uninstall the dewikartika package immediately using 'npm uninstall dewikartika' and audit your project for any other malicious dependencies.
You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
