Malicious code in awaitly-visualizer (npm)
The npm package awaitly-visualizer contains malicious code or depends on a package with malicious code. This malware, identified as Miasma, is a self-propagating worm that spreads through the npm registry by exploiting weaponized binding.gyp files to execute code during package installation. It attempts to exfiltrate credentials and OIDC tokens for cloud and registry services and propagates by compromising other packages or injecting backdoors into GitHub repositories. Multiple specific versions of awaitly-visualizer are affected.
AI Analysis
Technical Summary
The awaitly-visualizer npm package versions listed are affected by the Miasma malware, a self-propagating worm that abuses weaponized binding.gyp files to achieve execution during package installation, bypassing security tools that only inspect lifecycle scripts. Upon execution, it attempts credential and OIDC token exfiltration for various cloud and registry services and propagates by compromising other packages managed by stolen accounts or committing backdoor files to GitHub repositories. This threat leverages the npm ecosystem for propagation and credential theft.
Potential Impact
Malicious code execution during package installation can lead to credential and OIDC token theft for cloud and registry services. This enables further compromise of developer accounts and repositories, potentially leading to widespread supply chain attacks and unauthorized access to cloud resources. The malware's propagation mechanism increases the risk of infection across multiple packages and projects.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix or removal of malicious versions is confirmed, avoid using the affected versions of awaitly-visualizer. Verify package integrity through trusted sources and consider using alternative packages or versions not listed as affected. Monitor for updates from the package maintainers or npm security advisories regarding remediation.
Malicious code in awaitly-visualizer (npm)
Description
The npm package awaitly-visualizer contains malicious code or depends on a package with malicious code. This malware, identified as Miasma, is a self-propagating worm that spreads through the npm registry by exploiting weaponized binding.gyp files to execute code during package installation. It attempts to exfiltrate credentials and OIDC tokens for cloud and registry services and propagates by compromising other packages or injecting backdoors into GitHub repositories. Multiple specific versions of awaitly-visualizer are affected.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The awaitly-visualizer npm package versions listed are affected by the Miasma malware, a self-propagating worm that abuses weaponized binding.gyp files to achieve execution during package installation, bypassing security tools that only inspect lifecycle scripts. Upon execution, it attempts credential and OIDC token exfiltration for various cloud and registry services and propagates by compromising other packages managed by stolen accounts or committing backdoor files to GitHub repositories. This threat leverages the npm ecosystem for propagation and credential theft.
Potential Impact
Malicious code execution during package installation can lead to credential and OIDC token theft for cloud and registry services. This enables further compromise of developer accounts and repositories, potentially leading to widespread supply chain attacks and unauthorized access to cloud resources. The malware's propagation mechanism increases the risk of infection across multiple packages and projects.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix or removal of malicious versions is confirmed, avoid using the affected versions of awaitly-visualizer. Verify package integrity through trusted sources and consider using alternative packages or versions not listed as affected. Monitor for updates from the package maintainers or npm security advisories regarding remediation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5239
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4f6c7068715ace4315aa58
Added to database: 07/09/2026, 09:40:00 UTC
Last enriched: 07/09/2026, 10:07:57 UTC
Last updated: 07/30/2026, 16:26:20 UTC
Views: 21
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.