Malicious code in localize-translate (npm)
The npm package 'localize-translate' version 1.0.0 contains malicious code that executes during installation. Its postinstall script collects host identifiers such as hostname, platform, architecture, Node.js version, package name, timestamp, and npm lifecycle event, then sends this data as JSON to a hardcoded third-party server without user consent. This behavior constitutes an undisclosed, unconditional reconnaissance callback rather than legitimate telemetry.
AI Analysis
Technical Summary
The 'localize-translate' npm package version 1.0.0 includes a postinstall lifecycle script that collects installer host information (hostname, platform, architecture, Node.js version, package name, timestamp, and npm lifecycle event) and transmits it via HTTP POST to a hardcoded external endpoint (gigww0v7.instances.poc.jchunt.top/localize-translate). This transmission occurs automatically on every installation and is not disclosed to the user. The collected data is limited to host identity information and does not include credentials, filesystem data, or environment variables. The behavior is indicative of malicious reconnaissance activity embedded in the package.
Potential Impact
The impact involves unauthorized data exfiltration of host identifiers during package installation, potentially compromising user privacy and revealing environment details to a third party without consent. Although no credentials or sensitive filesystem data are collected, the unconditional and undisclosed nature of the data transmission constitutes a privacy and security risk.
Mitigation Recommendations
No official patch or remediation is currently available for this package version. Users should avoid installing 'localize-translate' version 1.0.0. Consider removing the package if already installed. Monitor for updates or advisories from the package maintainers or npm registry. Employ supply chain security best practices such as verifying package integrity and using trusted sources.
Malicious code in localize-translate (npm)
Description
The npm package 'localize-translate' version 1.0.0 contains malicious code that executes during installation. Its postinstall script collects host identifiers such as hostname, platform, architecture, Node.js version, package name, timestamp, and npm lifecycle event, then sends this data as JSON to a hardcoded third-party server without user consent. This behavior constitutes an undisclosed, unconditional reconnaissance callback rather than legitimate telemetry.
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 'localize-translate' npm package version 1.0.0 includes a postinstall lifecycle script that collects installer host information (hostname, platform, architecture, Node.js version, package name, timestamp, and npm lifecycle event) and transmits it via HTTP POST to a hardcoded external endpoint (gigww0v7.instances.poc.jchunt.top/localize-translate). This transmission occurs automatically on every installation and is not disclosed to the user. The collected data is limited to host identity information and does not include credentials, filesystem data, or environment variables. The behavior is indicative of malicious reconnaissance activity embedded in the package.
Potential Impact
The impact involves unauthorized data exfiltration of host identifiers during package installation, potentially compromising user privacy and revealing environment details to a third party without consent. Although no credentials or sensitive filesystem data are collected, the unconditional and undisclosed nature of the data transmission constitutes a privacy and security risk.
Mitigation Recommendations
No official patch or remediation is currently available for this package version. Users should avoid installing 'localize-translate' version 1.0.0. Consider removing the package if already installed. Monitor for updates or advisories from the package maintainers or npm registry. Employ supply chain security best practices such as verifying package integrity and using trusted sources.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-14279
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a85b4b4acd9273b49251553
Added to database: 08/19/2026, 13:50:44 UTC
Last enriched: 08/19/2026, 14:16:11 UTC
Last updated: 08/19/2026, 14:16:11 UTC
Views: 2
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.