Malicious Code Injection in Complicated Lark-Silentdev Package
Summary
MAL-2025-100787: Malicious code in complicated_lark-silentdev (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 'complicated_lark-silentdev' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the 'complicated_lark-silentdev' package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of variants. The ramifications include potential pollution of the npm registry, unauthorized access to sensitive data, and the risk of executing harmful scripts in dependent applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall complicated_lark-silentdevIf 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 'complicated_lark-silentdev' package from your project by executing the command: 'npm uninstall complicated_lark-silentdev'. This will prevent the execution of any malicious code until a secure version is available.
Conclusion
The 'complicated_lark-silentdev' package has been identified as containing malicious code that poses significant risks to applications using it. It is crucial to update or remove the package to safeguard your projects and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for complicated_lark-silentdev →
FAQ
The malicious code is designed to modify package.json files and republish variants with random names, which can lead to npm registry pollution.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
The risks include unauthorized access to sensitive data, execution of harmful scripts, and potential damage to the integrity of the npm registry.
Regularly updating packages and using tools like Vulert to monitor vulnerabilities can help prevent similar issues.
If immediate updates are not possible, consider uninstalling the package as a temporary measure to mitigate risks.
