Malicious code in frontend-vue-next (npm)
The npm package frontend-vue-next versions 1.0.0 and 1.2.0 contains malicious code that executes automatically during installation. The package runs a script that collects detailed system and user identity information and sends it to an attacker-controlled server. This behavior leaks sensitive host and user data without consent, posing a privacy and security risk to developers and CI environments.
AI Analysis
Technical Summary
The frontend-vue-next npm package declares a 'preinstall' script that runs index.js automatically on npm install. This script gathers system identity details including hostname, user information (username, uid, gid, shell), platform, architecture, home directory, current working directory, CPU and memory info. It also executes shell commands 'whoami' and 'id' to collect additional user identity data. All collected information is sent via HTTP POST to a hardcoded attacker-controlled URL (a Burp Suite Collaborator out-of-band domain). The package metadata is empty and the package name is designed to appear related to Vue/Next.js to lure victims. Versions 1.0.0 and 1.2.0 are affected.
Potential Impact
Installing the affected versions of frontend-vue-next results in unauthorized exfiltration of sensitive system and user identity information to an attacker-controlled server. This compromises the confidentiality of the host environment and user credentials, potentially enabling further targeted attacks or reconnaissance. The malicious behavior occurs silently during package installation, increasing the risk of unnoticed data leakage.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing frontend-vue-next versions 1.0.0 and 1.2.0. Verify package authenticity before installation and prefer well-known, verified packages. Monitor for suspicious network activity during npm installs. Check vendor or repository advisories for updates or removal of the malicious package.
Malicious code in frontend-vue-next (npm)
Description
The npm package frontend-vue-next versions 1.0.0 and 1.2.0 contains malicious code that executes automatically during installation. The package runs a script that collects detailed system and user identity information and sends it to an attacker-controlled server. This behavior leaks sensitive host and user data without consent, posing a privacy and security risk to developers and CI environments.
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 frontend-vue-next npm package declares a 'preinstall' script that runs index.js automatically on npm install. This script gathers system identity details including hostname, user information (username, uid, gid, shell), platform, architecture, home directory, current working directory, CPU and memory info. It also executes shell commands 'whoami' and 'id' to collect additional user identity data. All collected information is sent via HTTP POST to a hardcoded attacker-controlled URL (a Burp Suite Collaborator out-of-band domain). The package metadata is empty and the package name is designed to appear related to Vue/Next.js to lure victims. Versions 1.0.0 and 1.2.0 are affected.
Potential Impact
Installing the affected versions of frontend-vue-next results in unauthorized exfiltration of sensitive system and user identity information to an attacker-controlled server. This compromises the confidentiality of the host environment and user credentials, potentially enabling further targeted attacks or reconnaissance. The malicious behavior occurs silently during package installation, increasing the risk of unnoticed data leakage.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing frontend-vue-next versions 1.0.0 and 1.2.0. Verify package authenticity before installation and prefer well-known, verified packages. Monitor for suspicious network activity during npm installs. Check vendor or repository advisories for updates or removal of the malicious package.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2025-49410
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-7492-2cqc-6827"]
- Ecosystems
- ["npm"]
Threat ID: 6a96f318acd9273b49e4960b
Added to database: 09/01/2026, 15:45:28 UTC
Last enriched: 09/08/2026, 10:38:11 UTC
Last updated: 09/08/2026, 10:38:11 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.