Malicious code in @akunsansan0/pucuk12 (npm)
@akunsansan0/pucuk12 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/pucuk12
- Ecosystems
- Attack vectors
- Affected entities
- @akunsansan0/pucuk12
@akunsansan0/pucuk12 was identified as a malicious npm package containing 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.\n\nThis package was part of the tea.xyz token reward campaign that flooded npm with similar malicious packages. The attack was designed to inflate developer reputation scores for tea protocol token rewards.\n\nThe incident was identified and credited to the OpenSSF malicious-packages repository.
Indicators of compromise
- Packages
- @akunsansan0/pucuk12
Remediation
- Remove @akunsansan0/pucuk12 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 any unauthorized package publications
- Update to a clean version of any legitimate packages that may have been affected
- Monitor npm registry for similar malicious packages from the tea.xyz campaign
Sources
- GitHub Advisory GHSA-643r-p2hc-6r99 · GitHub Advisory Database
Cite this entry
"Malicious code in @akunsansan0/pucuk12 (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-pucuk12-npm-1letlq
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