Malicious Code Injection in spy-sun-byte-debug-import: A Threat to npm Ecosystem
Summary
MAL-2025-189632: Malicious code in spy-sun-byte-debug-import (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 'spy-sun-byte-debug-import' is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. Its functionality is compromised by malicious scripts that alter package metadata and continuously republish variants, leading to pollution of the npm registry.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the 'spy-sun-byte-debug-import' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The continuous republishing of these variants can lead to significant pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to further security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall spy-sun-byte-debug-importIf 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 'spy-sun-byte-debug-import' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The 'spy-sun-byte-debug-import' package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and repopulates the registry with harmful variants. It is crucial for developers to remove this package and utilize monitoring tools like Vulert to safeguard their applications.
See every vulnerability recorded for spy-sun-byte-debug-import →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and potentially exposing your project to further security risks.
You should uninstall the package immediately and monitor your project for any further vulnerabilities using tools like Vulert.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid installing packages from untrusted sources.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
