Skip to main content

Malicious code in @s4yhiitestpoc/r3-https (npm)

0
High
Published: 10/11/2026 (10/11/2026, 13:58:31 UTC)
Source: GCVE Database
Product: @s4yhiitestpoc/r3-https

Description

The npm package @s4yhiitestpoc/r3-https version 1.0.0 contains malicious code that collects extensive host and environment information during installation. This includes host identity, network interfaces, DNS settings, and project metadata, which it sends to a hardcoded external server without user consent. This behavior is indicative of reconnaissance activity commonly associated with dependency confusion attacks.

Affected software

npmghsa
@s4yhiitestpoc/r3-https
Affected versions
=1.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: 10/11/2026, 21:43:47 UTC

Technical Analysis

The malicious npm package @s4yhiitestpoc/r3-https (version 1.0.0) executes a post-install script that gathers detailed host information such as hostname, user identifiers, platform details, network interfaces, DNS servers, and container/runtime indicators. It also extracts the consuming project's package.json metadata by traversing parent directories. The collected data is exfiltrated via HTTPS POST requests and DNS lookups to a fixed external endpoint (collector.oob.s4yhii.com). This data leakage reveals private project identities and internal package naming, facilitating dependency confusion attack pipelines. The endpoint is hardcoded and not configurable, with no opt-out mechanism.

Potential Impact

The package leaks sensitive environment and project metadata to an external third party during installation, potentially exposing private project information and internal network details. This can aid attackers in crafting targeted dependency confusion attacks or other supply chain compromises. There is no indication of direct code execution beyond the data exfiltration, and 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 package version (=1.0.0). Since the endpoint is hardcoded and no opt-out exists, removing or replacing the package is the primary mitigation. Monitor for updates from the package maintainer or npm advisories for any official fixes.

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

Threat ID: 6acc00a32cdf04f656fecb2c

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

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

Last updated: 10/11/2026, 21:43:47 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