Malicious code in @akunsansan0/tea_nextgun (npm)
@akunsansan0/tea_nextgun is a malicious npm package containing autopublish scripts designed to automatically generate and republish derivative packages with randomized names to inflate developer reputation scores for tea protocol token rewards.
- Disclosed
- Last updated
- Blast radius
- npm registry; developers who installed this package
- Ecosystems
- Attack vectors
- Affected entities
- @akunsansan0/tea_nextgunnpm package containing malicious autopublish scripts
@akunsansan0/tea_nextgun is a malicious npm package identified as part of a broader campaign related to the tea.xyz token reward initiative. The package contains autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) that execute automatically upon installation.\n\nThe malicious payload modifies package.json to remove private flags and alter version numbers, then generates random package names (primarily Indonesian-themed variants, with some English variants) and continuously republishes these derivative packages to the npm registry. This behavior is designed to artificially inflate developer reputation scores and pollute the npm registry with spam packages.\n\nThe incident was identified by Amazon Inspector and credited to the OpenSSF malicious-packages project. The package has been flagged in the OpenSSF malicious packages database.
Indicators of compromise
- Packages
- @akunsansan0/tea_nextgun
Remediation
- Remove @akunsansan0/tea_nextgun from all projects immediately
- Audit package.json and lock files for any unexpected derivative packages with randomized names
- Review npm account activity for unauthorized package publications
- Clear npm cache and reinstall dependencies from a clean state
- Monitor npm account for suspicious activity related to tea protocol token campaigns
Sources
- GitHub Advisory GHSA-4h2w-43pr-xxqg · GitHub Advisory Database
Cite this entry
"Malicious code in @akunsansan0/tea_nextgun (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-tea-nextgun-npm-1jay3y
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- 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 - containedcritical
Malicious code in @antv/g-web-components (npm)
A threat actor compromised the npm account 'atool' and published 631 malicious versions across 314 npm packages in a 22-minute automated burst, including @antv/g-web-components. Each malicious version injects a preinstall hook executing an obfuscated Bun script that exfiltrates credentials and establishes persistence via CI/CD workflow injection and system daemons.
Mini Shai HuludnpmOtherAccount takeoverCompromised packageMalicious commit - containedcritical
Malicious code in @antv/dipper-hooks (npm)
The npm account `atool` was compromised and used to publish 631 malicious versions across 314 npm packages, including @antv/dipper-hooks, in an automated 22-minute burst. Each malicious version injects a preinstall hook executing an obfuscated Bun script that exfiltrates credentials (AWS keys, GitHub PATs, npm tokens, GCP service accounts, Azure credentials, Kubernetes tokens, SSH keys, Docker configs, database strings, Stripe keys, Slack tokens) via the GitHub API and establishes persistence through CI/CD workflow injection and system daemons.
Mini Shai HuludnpmOtherAccount takeoverCompromised packageMalicious commit - containedcritical
Malicious code in @antstackio/shelbysam (npm)
The npm package @antstackio/shelbysam was compromised and contained malicious code associated with the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials, publishes them to GitHub, propagates to other NPM packages owned by the user, and may destroy the user's home directory.
Shai-HuludnpmCompromised packageMalicious commit