Malicious code in @akunsansan0/karedok4 (npm)
@akunsansan0/karedok4 on npm contained malicious code designed to automatically generate and publish derivative packages with randomized names to inflate developer reputation scores for tea protocol token rewards. The package modified package.json, changed version numbers, and continuously republished variants to pollute the npm registry.
- Disclosed
- Last updated
- Blast radius
- npm registry; developers who installed @akunsansan0/karedok4
- Ecosystems
- Attack vectors
- Affected entities
- @akunsansan0/karedok4
@akunsansan0/karedok4 was identified as a malicious npm package part of the tea.xyz token reward campaign that flooded npm with fraudulent packages. The package contained autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) designed to automatically generate and publish derivative packages with randomized names.\n\nThe malicious payload modified package.json to remove private flags, changed version numbers, and generated random Indonesian-themed and English-themed package names. The package continuously republished variants to pollute the npm registry and inflate developer reputation scores for tea protocol token rewards.\n\nThe incident was identified by Amazon Inspector and credited to the OpenSSF malicious-packages repository. The package has been cataloged under MAL-2025-181311.
Indicators of compromise
- Packages
- @akunsansan0/karedok4
Remediation
- Remove @akunsansan0/karedok4 from all projects and dependencies
- Audit npm package.json files for any unexpected derivative packages with randomized names that may have been auto-published
- Review npm account activity for unauthorized package publications
- Update to a clean version of any legitimate packages that may have been affected
- Monitor npm registry for similar autopublish-based malicious packages
Sources
- GitHub Advisory GHSA-qjcv-hp23-v8w2 · GitHub Advisory Database
Cite this entry
"Malicious code in @akunsansan0/karedok4 (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 26, 2025; last updated July 26, 2026. https://supplychainattack.org/incident/malicious-code-in-akunsansan0-karedok4-npm-1ycze9
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit