Malicious code in internallib_v557 (npm)
The internallib_v557 npm package contains malicious code that performs a multi-step attack on an internal npm registry. It creates a persistent attacker user, publishes a malicious package version that exfiltrates sensitive data from the root user, and communicates with a hardcoded attacker server. Any system installing or running this package is considered fully compromised.
AI Analysis
Technical Summary
The internallib_v557 package implements a multi-step attack targeting an internal npm registry. Upon execution, it creates an attacker user on the registry, queries package metadata, writes authentication credentials locally, and publishes a malicious version of the 'uhclabs_local_check' package. This malicious package's start script exfiltrates the contents of /root/root.txt to a hardcoded attacker IP address. The attacker maintains persistent publishing access to the internal registry, enabling future malicious releases. This attack results in a namespace takeover with a command and control beacon embedded in the package, indicating no legitimate purpose for the code.
Potential Impact
Systems with this package installed or running are fully compromised, allowing attackers to exfiltrate sensitive files such as /root/root.txt. The attacker gains persistent access to the internal npm registry for future malicious package publishing. All secrets and keys stored on compromised systems should be considered exposed and require immediate rotation. Removing the package alone does not guarantee removal of all malicious software or attacker control.
Mitigation Recommendations
No official patch or fix is currently documented. Immediate removal of the internallib_v557 package is recommended. All secrets and keys on affected systems should be rotated from a separate, trusted environment. Due to the persistent nature of the compromise, assume full system compromise and consider rebuilding affected systems. Monitor internal npm registries for unauthorized users or packages and restrict publishing permissions. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Malicious code in internallib_v557 (npm)
Description
The internallib_v557 npm package contains malicious code that performs a multi-step attack on an internal npm registry. It creates a persistent attacker user, publishes a malicious package version that exfiltrates sensitive data from the root user, and communicates with a hardcoded attacker server. Any system installing or running this package is considered fully compromised.
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 internallib_v557 package implements a multi-step attack targeting an internal npm registry. Upon execution, it creates an attacker user on the registry, queries package metadata, writes authentication credentials locally, and publishes a malicious version of the 'uhclabs_local_check' package. This malicious package's start script exfiltrates the contents of /root/root.txt to a hardcoded attacker IP address. The attacker maintains persistent publishing access to the internal registry, enabling future malicious releases. This attack results in a namespace takeover with a command and control beacon embedded in the package, indicating no legitimate purpose for the code.
Potential Impact
Systems with this package installed or running are fully compromised, allowing attackers to exfiltrate sensitive files such as /root/root.txt. The attacker gains persistent access to the internal npm registry for future malicious package publishing. All secrets and keys stored on compromised systems should be considered exposed and require immediate rotation. Removing the package alone does not guarantee removal of all malicious software or attacker control.
Mitigation Recommendations
No official patch or fix is currently documented. Immediate removal of the internallib_v557 package is recommended. All secrets and keys on affected systems should be rotated from a separate, trusted environment. Due to the persistent nature of the compromise, assume full system compromise and consider rebuilding affected systems. Monitor internal npm registries for unauthorized users or packages and restrict publishing permissions. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5678
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-945p-4458-jg48"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4f6c4168715ace43158b46
Added to database: 07/09/2026, 09:39:13 UTC
Last enriched: 07/09/2026, 09:54:38 UTC
Last updated: 07/20/2026, 13:32:36 UTC
Views: 7
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.