Skip to main content

Malicious code in etoro-core (npm)

0
Medium
Published: 09/10/2026 (09/10/2026, 04:43:55 UTC)
Source: GCVE Database
Product: etoro-core

Description

The npm package 'etoro-core' version 999.0.0 contains malicious code in its preinstall lifecycle script. This script performs an HTTP GET request to a hardcoded attacker-controlled IP address, transmitting the host's identity information in plaintext during installation. This behavior is consistent with a dependency confusion attack targeting an internal package name.

Affected software

npmghsa
etoro-core
Affected versions
=999.0.0

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

AILast updated: 09/10/2026, 13:39:34 UTC

Technical Analysis

The 'etoro-core' npm package at version 999.0.0 includes a preinstall.js script that automatically executes during 'npm install'. This script sends an HTTP GET request to http://209.126.81.147/etoro-depconf-poce346552f776f/npm/ embedding the host's OS hostname, username, and current working directory in the URL path. This transmits sensitive installer host identity information over unencrypted HTTP to an attacker-controlled endpoint. The package name and inflated version number suggest it is a dependency confusion payload designed to impersonate an internal 'etoro-core' package.

Potential Impact

The malicious preinstall script leaks sensitive host environment information (hostname, username, working directory) to an attacker-controlled server over plaintext HTTP. This exposure can aid attackers in reconnaissance and further targeted attacks. There is no indication of additional payloads or code execution beyond data exfiltration. No known exploits in the wild have been reported.

Mitigation Recommendations

No official patch or remediation is currently documented. Users should avoid installing the 'etoro-core' package at version 999.0.0 from untrusted sources. Verify package authenticity before installation and monitor for updates or advisories from the package maintainers or npm registry. Since this is a malicious package likely introduced via dependency confusion, organizations should implement supply chain security best practices such as package allowlisting and internal package namespace enforcement.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
MAL-2026-16120
Osv Schema Version
1.7.4
Ecosystems
["npm"]

Threat ID: 6aa2af89acd9273b4925b52a

Added to database: 09/10/2026, 13:24:25 UTC

Last enriched: 09/10/2026, 13:39:34 UTC

Last updated: 09/11/2026, 15:19:01 UTC

Views: 12

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses