Malicious Code Detected in structural_heron_dumbs: A Threat to npm Packages
Summary
MAL-2025-109212: Malicious code in structural_heron_dumbs (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 'structural_heron_dumbs' is part of a broader ecosystem within npm, primarily associated with the tea.xyz token reward campaign. 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 manipulate package metadata, leading to potential abuse within the npm registry.
Vulnerability Detail
The vulnerability in 'structural_heron_dumbs' originates from its association with malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The malicious payload is designed to continuously republish variants of the package, potentially affecting developers' reputations and the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall structural_heron_dumbsIf 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 remove the 'structural_heron_dumbs' package from your project by executing: npm uninstall structural_heron_dumbs. This will prevent any malicious code from executing while you assess the situation.
Conclusion
The 'structural_heron_dumbs' package poses a significant threat due to its malicious code that alters package metadata and republish variants. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for structural_heron_dumbs →
FAQ
The main issue is the presence of malicious code that modifies package metadata and republish variants, which can lead to npm registry pollution.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
The consequences include damage to developer reputation, potential security risks, and the integrity of the npm ecosystem being compromised.
Regularly updating packages, using tools like Vulert to monitor vulnerabilities, and conducting security audits can help prevent similar issues.
You can reach out to Amazon Inspector at actran@amazon.com for more information regarding this vulnerability.
