Malicious code in awaitly-postgres (npm)
The npm package awaitly-postgres contains malicious code identified as the Miasma malware. This malware is a self-propagating worm that spreads by abusing weaponized binding.gyp files during package installation, bypassing security tools that only inspect lifecycle scripts. It attempts to exfiltrate credentials and OIDC tokens for cloud and registry services and propagates by compromising other packages or committing backdoor files to GitHub repositories. Multiple specific versions of awaitly-postgres are affected.
AI Analysis
Technical Summary
The awaitly-postgres npm package versions listed contain malicious code known as Miasma malware. This malware leverages weaponized binding.gyp files to execute during package installation, evading detection by security tools focused on lifecycle scripts. Once executed, it attempts credential and token exfiltration for various cloud and registry services and spreads by compromising additional packages and repositories. This represents a supply chain threat within the npm ecosystem.
Potential Impact
Affected versions of awaitly-postgres may lead to credential and OIDC token theft for cloud and registry services, enabling unauthorized access. The malware can propagate further by compromising other packages and injecting backdoors into GitHub repositories, increasing the risk of widespread compromise in development environments relying on these packages.
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, users should avoid using the affected versions of awaitly-postgres. Consider auditing dependencies and replacing or removing compromised packages. Monitor official advisories for updates on remediation.
Malicious code in awaitly-postgres (npm)
Description
The npm package awaitly-postgres contains malicious code identified as the Miasma malware. This malware is a self-propagating worm that spreads by abusing weaponized binding.gyp files during package installation, bypassing security tools that only inspect lifecycle scripts. It attempts to exfiltrate credentials and OIDC tokens for cloud and registry services and propagates by compromising other packages or committing backdoor files to GitHub repositories. Multiple specific versions of awaitly-postgres 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-postgres npm package versions listed contain malicious code known as Miasma malware. This malware leverages weaponized binding.gyp files to execute during package installation, evading detection by security tools focused on lifecycle scripts. Once executed, it attempts credential and token exfiltration for various cloud and registry services and spreads by compromising additional packages and repositories. This represents a supply chain threat within the npm ecosystem.
Potential Impact
Affected versions of awaitly-postgres may lead to credential and OIDC token theft for cloud and registry services, enabling unauthorized access. The malware can propagate further by compromising other packages and injecting backdoors into GitHub repositories, increasing the risk of widespread compromise in development environments relying on these packages.
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, users should avoid using the affected versions of awaitly-postgres. Consider auditing dependencies and replacing or removing compromised packages. Monitor official advisories for updates on remediation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5238
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4f6c7468715ace4315abeb
Added to database: 07/09/2026, 09:40:04 UTC
Last enriched: 07/09/2026, 10:08:02 UTC
Last updated: 07/30/2026, 04:18:08 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.