Skip to main content

Malicious code in another-very-long-name (npm)

0
High
Published: 10/11/2026 (10/11/2026, 13:54:57 UTC)
Source: GCVE Database
Product: another-very-long-name

Description

The npm package 'another-very-long-name' versions 1.0.1, 1.1.0, 2.0.0, and 2.0.1 contain malicious code that collects host system identifiers and sends them to a hardcoded external IP address via an unencrypted HTTP POST request. The package does not provide genuine functionality and appears to be designed for reconnaissance, likely related to dependency confusion attacks.

Affected software

npmghsa
another-very-long-name
Affected versions
=2.0.0=1.0.1=2.0.1=1.1.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: 10/11/2026, 21:43:19 UTC

Technical Analysis

The 'another-very-long-name' npm package in versions 1.0.1, 1.1.0, 2.0.0, and 2.0.1 includes a beacon.cjs script executed during postinstall and module require time. This script collects host identifiers such as hostname, installation path, current working directory, Node.js version, OS metadata, and the package name, then sends this data as JSON to a hardcoded cleartext HTTP endpoint at 185.158.107.175:8787. The package's main module exports a Proxy object that returns no-op functions to avoid bundler errors, indicating the package's primary purpose is data collection rather than functionality. The external endpoint has no known relationship to the package publisher, and the behavior aligns with reconnaissance activity consistent with dependency confusion attack probes.

Potential Impact

The malicious package can exfiltrate sensitive host environment information without user consent, potentially aiding attackers in mapping victim environments for further exploitation. The use of an unencrypted HTTP endpoint exposes the data to interception. There is no indication of direct code execution beyond data collection, and no known active exploitation in the wild has been reported.

Mitigation Recommendations

No official patch or remediation guidance is provided. Users should avoid installing or using the affected versions (=1.0.1, =1.1.0, =2.0.0, =2.0.1) of the 'another-very-long-name' package. Review and remove the package from projects if present. Consider using trusted package sources and verifying package integrity before installation.

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-17767
Osv Schema Version
1.7.4
Ecosystems
["npm"]

Threat ID: 6acc00a32cdf04f656fecb08

Added to database: 10/11/2026, 21:33:23 UTC

Last enriched: 10/11/2026, 21:43:19 UTC

Last updated: 10/11/2026, 21:43:19 UTC

Views: 2

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