Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @taxify published 10 malicious packages. See the full campaign →
Malicious package

@taxify/eslint-config-react-nativenpm

@taxify/eslint-config-react-native is a confirmed malicious npm package (MAL-2024-7898) that executes malicious code on install (malicious versions 8.999.0, 9.999.0, 10.0.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @taxify/eslint-config-react-native (npm)

MAL-2024-7898
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @taxify/eslint-config-react-native

What this malware does

The OpenSSF Package Analysis project identified '@taxify/eslint-config-react-native' @ 9.999.0 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

5 flagged
8.999.09.999.010.0.010.0.110.0.5

Indicators of compromise (SHA-256)

5cff605dafce45695b36c5a3ca744b5187bab414e45e390d8e4ac966f6088573
d33b097b40a9cd716d70971284f8d22edaf297eb8092eaf08cf58fa5e39bc4ef
c2f0dfc0513571155991ab7ba6391685cb966d165591797e684a01c627d913e8

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @taxify/eslint-config-react-native (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @taxify/eslint-config-react-native across your stack and pipelines.

  2. If you installed it — respond

    Remove @taxify/eslint-config-react-native from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @taxify/eslint-config-react-native was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks @taxify/eslint-config-react-native before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @taxify/eslint-config-react-native on npm has been identified as a malicious package (versions 8.999.0, 9.999.0, 10.0.0, 10.0.1, 10.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-06048

Credits

  • OpenSSF: Package Analysis · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @taxify/eslint-config-react-native-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

@taxify/eslint-config-react-native (npm) malicious package — MAL-2024-7898 | O3 Security