Malicious code in @akunsansan0/pucuk9 (npm)
The npm package @akunsansan0/pucuk9 contained malicious code designed to automatically generate and publish derivative packages with randomized names to the npm registry. The package was part of a broader campaign to inflate developer reputation scores for tea protocol token rewards.
- Disclosed
- Last updated
- Blast radius
- npm registry; developers who installed @akunsansan0/pucuk9
- Ecosystems
- Attack vectors
- Affected entities
- @akunsansan0/pucuk9
The npm package @akunsansan0/pucuk9 was identified as containing malicious code by Amazon Inspector and credited to OpenSSF's malicious-packages repository. The package included autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) designed to automatically generate and republish derivative packages.\n\nThe malicious payload modified package.json files to remove private flags, altered version numbers, and generated random package names with Indonesian and English themes. The scripts continuously republished variants to pollute the npm registry.\n\nThis package was part of a broader tea.xyz token reward campaign that flooded npm with similar malicious packages. The campaign exploited npm's publishing mechanisms to artificially inflate developer reputation scores for tea protocol token rewards.\n\nThe incident has been documented in the OpenSSF's malicious-packages repository (MAL-2025-181332).
Indicators of compromise
- Packages
- @akunsansan0/pucuk9
Remediation
- Remove @akunsansan0/pucuk9 from all dependencies and lock files
- Audit npm package.json and lock files for any unexpected derivative packages with randomized names
- Review npm account activity for unauthorized package publications
- Update to a clean version of any affected projects
- Monitor npm registry for similar malicious packages from the tea.xyz campaign
Sources
- GitHub Advisory GHSA-j4vr-26mm-q9fp · GitHub Advisory Database
Cite this entry
"Malicious code in @akunsansan0/pucuk9 (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 26, 2026; last updated July 26, 2026. https://supplychainattack.org/incident/malicious-code-in-akunsansan0-pucuk9-npm-10n6dv
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in @aligntech-cw/alignerfit (npm)
Malicious code was discovered in the npm package @aligntech-cw/alignerfit. The package was identified by the OpenSSF malicious-packages project and assigned identifier MAL-2024-1743.
npmCompromised package - resolvedcritical
Malicious code in @akunsansan0/susu10 (npm)
@akunsansan0/susu10 is a malicious npm package containing autopublish scripts designed to automatically generate and republish derivative packages with randomized names to the npm registry. The package was part of a tea.xyz token reward campaign that flooded npm with similar malicious packages.
npmCompromised package - containedcritical
Malicious code in @antv/f-wx (npm)
The npm account `atool` was compromised and used to publish 631 malicious versions across 314 packages, including @antv/f-wx. Each version injects a preinstall hook executing an obfuscated Bun script that exfiltrates credentials via the GitHub API and establishes persistence through CI/CD workflow injection and system daemons.
Mini Shai HuludTeamPCPnpmOtherAccount takeoverCompromised packageMalicious commit - resolvedcritical
Malicious code in @akunsansan0/susu11 (npm)
@akunsansan0/susu11 is a malicious npm package containing autopublish scripts designed to automatically generate and republish derivative packages with randomized names to inflate tea protocol token rewards. The package modifies package.json, changes version numbers, and continuously pollutes the npm registry with variants.
npmCompromised package