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

GHSA-4rx9-58m7-gr8w

GHSA-4rx9-58m7-gr8w is a security vulnerability in css_transform_step. O3 Security confirms whether GHSA-4rx9-58m7-gr8w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Malicious Package in css_transform_step

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

Real-World Exposure

1 pkg affected
📦css_transform_step

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Version 1.0.6 of css_transform_step contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to https://js-metrics.com/minjs.php?pl=

Recommendation

If version 1.0.6 of this module is found installed you will want to replace it with a version before or after 1.0.6. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.

Users may consider downgrading to version 1.0.5

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmcss_transform_stepall 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 css_transform_step. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of css_transform_step has shipped for GHSA-4rx9-58m7-gr8w 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-4rx9-58m7-gr8w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-4rx9-58m7-gr8w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Version 1.0.6 of `css_transform_step` contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=` ## Recommendation If version 1.0.6 of this module is found installed you will want to replace it with a version before or after 1.0.6. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised. Users may consider downgrading to version 1.0.5
O3 Security · Impact-Aware SCA

Is GHSA-4rx9-58m7-gr8w in your dependencies?

O3 detects GHSA-4rx9-58m7-gr8w across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-4rx9-58m7-gr8w: Malicious Package in… | O3 Security