Which versions of dialogflow-es are malicious?

The following npm versions of dialogflow-es are flagged malicious: 1.1.1, 1.1.2, 1.1.3, 1.1.4. Treat any of these as compromised.

How do I remediate dialogflow-es if I installed it?

dialogflow-es is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed dialogflow-es — how do I know if it already compromised me?

If dialogflow-es was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is dialogflow-es part of a known attack campaign?

Yes — dialogflow-es is associated with the RLMA-2025-06112 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find dialogflow-es across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dialogflow-es (4 malicious versions).

Malicious package

dialogflow-esnpm

Advisory published Nov 25, 2025Updated Dec 23, 2025

dialogflow-es is a confirmed malicious npm package (MAL-2025-191393) that steals credentials and exfiltrates sensitive data (malicious versions 1.1.1, 1.1.2, 1.1.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dialogflow-es (npm)

MAL-2025-191393

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall dialogflow-es

What this malware does

The package dialogflow-es was found to contain malicious code.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

4 flagged

1.1.11.1.21.1.31.1.4

Indicators of compromise (SHA-256)

7b2575b9b9549c778a241243c60685d266f19671c6803d5a422bfc57a677e318

bc28670a312b03ed84a92c48dcc51356053c6dc516a8360a44e47eed31815486

38d90dbfae6dd6ce815799fc6fd667262bc9a62039edd83add034285a2d4abad

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for dialogflow-es (4 malicious versions).
If you installed it — respond
dialogflow-es is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If dialogflow-es was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dialogflow-es on npm has been identified as a malicious package (versions 1.1.1, 1.1.2, 1.1.3, 1.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06112

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks dialogflow-es-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database