Which versions of @lessondesk/babel-preset are malicious?

The following npm versions of @lessondesk/babel-preset are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate @lessondesk/babel-preset if I installed it?

@lessondesk/babel-preset 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 @lessondesk/babel-preset — how do I know if it already compromised me?

If @lessondesk/babel-preset 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 @lessondesk/babel-preset part of a known attack campaign?

Yes — @lessondesk/babel-preset is associated with the GHSA-92j3-565q-xc26 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 @lessondesk/babel-preset across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @lessondesk/babel-preset (version 1.0.1).

Malicious package

@lessondesk/babel-presetnpm

Advisory published Nov 24, 2025Updated Dec 1, 2025

@lessondesk/babel-preset is a confirmed malicious npm package (MAL-2025-191027) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @lessondesk/babel-preset (npm)

MAL-2025-191027

Immediate action

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

npm uninstall @lessondesk/babel-preset

What this malware does

The package @lessondesk/babel-preset was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

1 flagged

1.0.1

Indicators of compromise (SHA-256)

b1dab5bbf04d256ff8f918c245175b34492065b8917a13230739ada1aa9180e4

a4b440b370b59f89e9fe1c0f63667b09dfd18f08ce66f20425c63c615db9873c

fa9019603bb68a67d97d54238e2318b1dcfdb801519fbb4b19d881b139cb7e13

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @lessondesk/babel-preset (version 1.0.1).
If you installed it — respond
@lessondesk/babel-preset 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 @lessondesk/babel-preset 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. @lessondesk/babel-preset on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-92j3-565q-xc26

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @lessondesk/babel-preset-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