MalwarePublished 6 Aug 2026

@lyxa.ai/core (npm) · Malicious Code

Affects @lyxa.ai/coreSource GCVE Database

Malicious package : remove @lyxa.ai/core and rotate any secrets on hosts that installed it.

Data as of 7 Aug 2026, 07:17 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-13434

What to do

Remove @lyxa.ai/core from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npm@lyxa.ai/core	Affected 1.0.8-debug-1 – 1.2.43 20 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

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

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.

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.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Aug 2026, 07:17 UTC

Technical details

References

Community reviews