Malicious code in nat-ulid (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ab95c3f95c377215b7cbd4be6d2cdcc79304910b03a2dcdf08f65da6f1c05f4c) The package ships a bundled file at dist/node/payload.js containing several POST call sites (around lines 14592, 14621, 14805, 14923, 15805). Pattern matches alone cannot distinguish a legitimate HTTP client library from an exfiltration channel: the destinations may be configurable parameters of an exposed API, documented vendor endpoints, or attacker-controlled hosts. No corroborating behavior such as credential reads, environment scraping, install-time lifecycle execution, or known-bad infrastructure was identified in the available evidence. Routing to human review for semantic verification of the bundle's POST destinations and reachability. ## Source: ghsa-malware (86093a5f138b04098b5998320eba1e20458181cbc3b0d71e27cb3aa234245396) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
The nat-ulid package version 3.0.2 includes a bundled file (dist/node/payload.js) with several POST call sites that may be used for data exfiltration. While pattern matching cannot definitively distinguish legitimate from malicious HTTP traffic, the presence of multiple POST requests in this context is suspicious. No direct evidence of credential theft or environment scraping was identified, but the package is flagged as malicious by the GHSA-malware source, indicating full compromise of affected systems. The package should be removed and secrets rotated, but full remediation may require additional incident response due to potential persistent compromise.
Potential Impact
Any computer with nat-ulid version 3.0.2 installed or running should be considered fully compromised. Attackers may have gained full control, risking exposure of all stored secrets and keys. Simply removing the package may not remove all malicious artifacts, increasing the risk of ongoing unauthorized access.
Mitigation Recommendations
Remove the nat-ulid package version 3.0.2 immediately from all affected systems. Rotate all secrets and keys from a separate, uncompromised system. Conduct a thorough incident response to identify and remediate any persistent malicious components beyond the package itself. Patch status is not applicable as this is a malicious package rather than a vulnerability with a vendor fix.
Malicious code in nat-ulid (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ab95c3f95c377215b7cbd4be6d2cdcc79304910b03a2dcdf08f65da6f1c05f4c) The package ships a bundled file at dist/node/payload.js containing several POST call sites (around lines 14592, 14621, 14805, 14923, 15805). Pattern matches alone cannot distinguish a legitimate HTTP client library from an exfiltration channel: the destinations may be configurable parameters of an exposed API, documented vendor endpoints, or attacker-controlled hosts. No corroborating behavior such as credential reads, environment scraping, install-time lifecycle execution, or known-bad infrastructure was identified in the available evidence. Routing to human review for semantic verification of the bundle's POST destinations and reachability. ## Source: ghsa-malware (86093a5f138b04098b5998320eba1e20458181cbc3b0d71e27cb3aa234245396) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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 nat-ulid package version 3.0.2 includes a bundled file (dist/node/payload.js) with several POST call sites that may be used for data exfiltration. While pattern matching cannot definitively distinguish legitimate from malicious HTTP traffic, the presence of multiple POST requests in this context is suspicious. No direct evidence of credential theft or environment scraping was identified, but the package is flagged as malicious by the GHSA-malware source, indicating full compromise of affected systems. The package should be removed and secrets rotated, but full remediation may require additional incident response due to potential persistent compromise.
Potential Impact
Any computer with nat-ulid version 3.0.2 installed or running should be considered fully compromised. Attackers may have gained full control, risking exposure of all stored secrets and keys. Simply removing the package may not remove all malicious artifacts, increasing the risk of ongoing unauthorized access.
Mitigation Recommendations
Remove the nat-ulid package version 3.0.2 immediately from all affected systems. Rotate all secrets and keys from a separate, uncompromised system. Conduct a thorough incident response to identify and remediate any persistent malicious components beyond the package itself. Patch status is not applicable as this is a malicious package rather than a vulnerability with a vendor fix.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5880
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-wgqj-fphq-9x3q"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50ba4c68715ace4357ea41
Added to database: 07/10/2026, 09:24:28 UTC
Last enriched: 07/10/2026, 09:38:41 UTC
Last updated: 07/18/2026, 17:27:21 UTC
Views: 4
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.
External Links
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.