How severe is GHSA-5x7p-gm79-383m?

GHSA-5x7p-gm79-383m has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-5x7p-gm79-383m?

GHSA-5x7p-gm79-383m affects the following packages: regenraotr (npm). Ecosystems affected: npm.

How do I fix GHSA-5x7p-gm79-383m?

No patched version of regenraotr has shipped for GHSA-5x7p-gm79-383m yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-5x7p-gm79-383m in my npm dependencies?

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

How do I mitigate GHSA-5x7p-gm79-383m if there is no patch (or I can't update yet)?

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.

Is GHSA-5x7p-gm79-383m actively exploited in the wild?

No public exploit code has been indexed for GHSA-5x7p-gm79-383m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-5x7p-gm79-383m published, and has it been updated?

GHSA-5x7p-gm79-383m was published on September 1, 2020 and was last updated on October 1, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

CRITICAL severity

Malicious Package in regenraotrGHSA-5x7p-gm79-383m

CRITICAL

GHSA-5x7p-gm79-383m is a critical-severity (CVSS 9.8) vulnerability in regenraotr. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 1, 2020

Updated

Oct 1, 2021

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Oct 1, 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.

regenraotrnpm

68downloads / week

Description

All versions of regenraotr are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands.

Recommendation

This package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`regenraotr`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for regenraotr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of regenraotr has shipped for GHSA-5x7p-gm79-383m yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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

All versions of `regenraotr` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands. ## Recommendation This package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.

O3 Security · Impact-Aware SCA

Is GHSA-5x7p-gm79-383m in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works