Malicious code in @depup/astro (npm)
The @depup/astro npm package is a malicious package impersonating the legitimate Astro framework by using similar but fake dependency names and altered source code. It replaces genuine dependencies with lookalike packages controlled by different maintainers, potentially introducing malicious code during installation and build. The package advertises misleading version numbers and uses keywords to appear as a routine maintenance update.
AI Analysis
Technical Summary
The @depup/astro package published under the @depup scope masquerades as a legitimate dependency-bump of the Astro framework by setting the author to 'withastro' and repository to the official Astro GitHub. However, it replaces well-known Astro dependencies with similarly named lookalike packages controlled by different maintainers (e.g., picocolors replaced by piccolore, debug by obug). The source code is mass-rewritten to import these lookalikes, causing npm install and builds to resolve and execute potentially malicious code from these fake dependencies. The advertised version numbers do not correspond to real upstream releases, and keywords like 'security', 'latest', and 'patched' are used deceptively to normalize these substitutions as legitimate updates.
Potential Impact
Users who install and build projects depending on @depup/astro versions =7.1.3-depup.2 or =7.2.0-depup.0 may unknowingly execute malicious code from the substituted lookalike dependencies. This can lead to compromise of the build environment or downstream applications relying on this package. No known exploits in the wild have been reported yet.
Mitigation Recommendations
No official patch or fix is indicated in the provided data. Users should avoid installing or using the @depup/astro package versions =7.1.3-depup.2 and =7.2.0-depup.0. Verify dependencies carefully to ensure they come from trusted sources and use genuine package names. Monitor vendor advisories or npm security advisories for updates or official remediation guidance.
Malicious code in @depup/astro (npm)
Description
The @depup/astro npm package is a malicious package impersonating the legitimate Astro framework by using similar but fake dependency names and altered source code. It replaces genuine dependencies with lookalike packages controlled by different maintainers, potentially introducing malicious code during installation and build. The package advertises misleading version numbers and uses keywords to appear as a routine maintenance update.
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 @depup/astro package published under the @depup scope masquerades as a legitimate dependency-bump of the Astro framework by setting the author to 'withastro' and repository to the official Astro GitHub. However, it replaces well-known Astro dependencies with similarly named lookalike packages controlled by different maintainers (e.g., picocolors replaced by piccolore, debug by obug). The source code is mass-rewritten to import these lookalikes, causing npm install and builds to resolve and execute potentially malicious code from these fake dependencies. The advertised version numbers do not correspond to real upstream releases, and keywords like 'security', 'latest', and 'patched' are used deceptively to normalize these substitutions as legitimate updates.
Potential Impact
Users who install and build projects depending on @depup/astro versions =7.1.3-depup.2 or =7.2.0-depup.0 may unknowingly execute malicious code from the substituted lookalike dependencies. This can lead to compromise of the build environment or downstream applications relying on this package. No known exploits in the wild have been reported yet.
Mitigation Recommendations
No official patch or fix is indicated in the provided data. Users should avoid installing or using the @depup/astro package versions =7.1.3-depup.2 and =7.2.0-depup.0. Verify dependencies carefully to ensure they come from trusted sources and use genuine package names. Monitor vendor advisories or npm security advisories for updates or official remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13622
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a774329bf8831d539b45d2a
Added to database: 08/08/2026, 14:54:33 UTC
Last enriched: 08/08/2026, 15:37:04 UTC
Last updated: 08/08/2026, 20:00:42 UTC
Views: 5
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.