Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

Malicious Package in yeoman-genratorGHSA-fm7r-2pr7-rw2p

CRITICAL

GHSA-fm7r-2pr7-rw2p is a critical-severity (CVSS 9.8) vulnerability in yeoman-genrator. No vendor fix is recorded yet; mitigation options are listed below.

Published
Updated
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Sep 30, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

yeoman-genratornpm
7downloads / week

Description

Version 3.1.1 of yeoman-genrator contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.

Recommendation

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.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmyeoman-genratorall versionsNo fix

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for yeoman-genrator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of yeoman-genrator has shipped for GHSA-fm7r-2pr7-rw2p yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Version 3.1.1 of `yeoman-genrator` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor. ## Recommendation 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
O3 Security · Impact-Aware SCA

Is GHSA-fm7r-2pr7-rw2p in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Malicious Package in yeoman-genrator (Critical 9.8)