Malicious code in @lyxa.ai/core (npm)
The @lyxa.ai/core npm package contains malicious code that embeds hardcoded credentials for cloud services controlled by the package author. These include AMQP broker credentials, Redis Cloud credentials, and GCP service account private keys. This allows any party with access to these credentials to send arbitrary messages that trigger code execution in the installer's environment and gain administrative access to cloud resources used by the package.
AI Analysis
Technical Summary
The exported bootstrapCore() function in @lyxa.ai/core unconditionally initializes an event bus with a hardcoded AMQPS URL containing embedded credentials for the author's CloudAMQP broker. This setup allows any party possessing these credentials to publish messages that invoke arbitrary subscriber methods in the installer's process. Additionally, the package defaults to a hardcoded Redis Cloud endpoint with embedded credentials and includes a GCP SecretManagerServiceClient instantiated with a shipped service-account private key. The compiled bundle contains live private keys for multiple GCP projects and Firebase Admin keys, along with Redis and CloudAMQP credentials. This effectively grants third parties administrative access to the author-controlled cloud backends that the package depends on, enabling unauthorized access and potential control over installer cache, secret lookups, and database operations.
Potential Impact
Attackers with access to the embedded credentials can execute arbitrary code within the installer's environment by sending crafted AMQP messages. They can also access and manipulate cloud resources including Redis caches, GCP secrets, MongoDB databases, and Firebase projects controlled by the package author. This compromises confidentiality, integrity, and availability of data and services relying on these cloud resources.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix or update is available, avoid using the affected versions of the @lyxa.ai/core package. Consider auditing your dependencies for this package and removing or replacing it to prevent exposure to the embedded malicious credentials and backdoor access.
Malicious code in @lyxa.ai/core (npm)
Description
The @lyxa.ai/core npm package contains malicious code that embeds hardcoded credentials for cloud services controlled by the package author. These include AMQP broker credentials, Redis Cloud credentials, and GCP service account private keys. This allows any party with access to these credentials to send arbitrary messages that trigger code execution in the installer's environment and gain administrative access to cloud resources used by the package.
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 exported bootstrapCore() function in @lyxa.ai/core unconditionally initializes an event bus with a hardcoded AMQPS URL containing embedded credentials for the author's CloudAMQP broker. This setup allows any party possessing these credentials to publish messages that invoke arbitrary subscriber methods in the installer's process. Additionally, the package defaults to a hardcoded Redis Cloud endpoint with embedded credentials and includes a GCP SecretManagerServiceClient instantiated with a shipped service-account private key. The compiled bundle contains live private keys for multiple GCP projects and Firebase Admin keys, along with Redis and CloudAMQP credentials. This effectively grants third parties administrative access to the author-controlled cloud backends that the package depends on, enabling unauthorized access and potential control over installer cache, secret lookups, and database operations.
Potential Impact
Attackers with access to the embedded credentials can execute arbitrary code within the installer's environment by sending crafted AMQP messages. They can also access and manipulate cloud resources including Redis caches, GCP secrets, MongoDB databases, and Firebase projects controlled by the package author. This compromises confidentiality, integrity, and availability of data and services relying on these cloud resources.
Defensive Guidance
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix or update is available, avoid using the affected versions of the @lyxa.ai/core package. Consider auditing your dependencies for this package and removing or replacing it to prevent exposure to the embedded malicious credentials and backdoor access.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13434
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7573b6bf8831d539d93c0f
Added to database: 08/07/2026, 05:57:10 UTC
Last enriched: 08/07/2026, 07:17:24 UTC
Last updated: 08/07/2026, 07:17:24 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.
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.