Malicious code in next-locomotive-init (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (9a11400eaa7dd74b24610ec815438de047089be7005b94c37717fa2b6f916ab6) The package's declared postinstall script reads the installer's OS username via os.userInfo().username and the machine hostname via os.hostname(), composes them into a `<username>@<hostname>` identifier, and POSTs them to a hardcoded remote endpoint at https://seedance2-api.vercel.app/api/agent/register together with a `source: 'next-locomotive-init'` tag. The package is advertised as animation utilities for Next.js templates; there is no functional or documented reason to transmit host identifiers to a third-party endpoint on install. The transmission fires automatically as a lifecycle script on `npm install` with no opt-in, no configuration, and no disclosure, giving the operator of that endpoint a census of every machine that installs the package — a beacon consistent with reconnaissance for follow-on targeting.
AI Analysis
Technical Summary
The next-locomotive-init npm package versions 1.0.0 through 1.0.4 include a malicious postinstall lifecycle script. This script uses Node.js os.userInfo().username and os.hostname() to gather the local machine's username and hostname, concatenates them into a <username>@<hostname> string, and sends this data via an HTTP POST request to a hardcoded external URL (https://seedance2-api.vercel.app/api/agent/register) with a source tag identifying the package. This data exfiltration occurs silently with no opt-in or notification, potentially enabling the remote operator to build a census of machines installing the package, which is consistent with reconnaissance activity for further targeting.
Potential Impact
The impact is the unauthorized exfiltration of host identifiers (username and hostname) from machines installing the affected package versions. This leakage of environment-specific information can facilitate attacker reconnaissance and profiling of victims. There is no indication of further exploitation or payload delivery within the package itself. No known exploits in the wild have been reported.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing the affected versions (=1.0.0, =1.0.1, =1.0.2, =1.0.3, =1.0.4) of next-locomotive-init. If already installed, remove the package and consider scanning for other malicious dependencies. Monitor vendor advisories or repository updates for any official fixes or guidance. Since this is not a cloud service, remediation depends on user action.
Malicious code in next-locomotive-init (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (9a11400eaa7dd74b24610ec815438de047089be7005b94c37717fa2b6f916ab6) The package's declared postinstall script reads the installer's OS username via os.userInfo().username and the machine hostname via os.hostname(), composes them into a `<username>@<hostname>` identifier, and POSTs them to a hardcoded remote endpoint at https://seedance2-api.vercel.app/api/agent/register together with a `source: 'next-locomotive-init'` tag. The package is advertised as animation utilities for Next.js templates; there is no functional or documented reason to transmit host identifiers to a third-party endpoint on install. The transmission fires automatically as a lifecycle script on `npm install` with no opt-in, no configuration, and no disclosure, giving the operator of that endpoint a census of every machine that installs the package — a beacon consistent with reconnaissance for follow-on targeting.
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 next-locomotive-init npm package versions 1.0.0 through 1.0.4 include a malicious postinstall lifecycle script. This script uses Node.js os.userInfo().username and os.hostname() to gather the local machine's username and hostname, concatenates them into a <username>@<hostname> string, and sends this data via an HTTP POST request to a hardcoded external URL (https://seedance2-api.vercel.app/api/agent/register) with a source tag identifying the package. This data exfiltration occurs silently with no opt-in or notification, potentially enabling the remote operator to build a census of machines installing the package, which is consistent with reconnaissance activity for further targeting.
Potential Impact
The impact is the unauthorized exfiltration of host identifiers (username and hostname) from machines installing the affected package versions. This leakage of environment-specific information can facilitate attacker reconnaissance and profiling of victims. There is no indication of further exploitation or payload delivery within the package itself. No known exploits in the wild have been reported.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing the affected versions (=1.0.0, =1.0.1, =1.0.2, =1.0.3, =1.0.4) of next-locomotive-init. If already installed, remove the package and consider scanning for other malicious dependencies. Monitor vendor advisories or repository updates for any official fixes or guidance. Since this is not a cloud service, remediation depends on user action.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-7013
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a520ec868715ace438f5eaf
Added to database: 07/11/2026, 09:37:12 UTC
Last enriched: 07/11/2026, 09:56:45 UTC
Last updated: 07/27/2026, 00:31:09 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.
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.