Malware in @meli-testing/jest-react
Malware discovered in the npm package @meli-testing/jest-react. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @meli-testing/jest-react
A malicious package named @meli-testing/jest-react was published to npm and contains malware. Any computer that has installed or executed this package should be considered fully compromised.\n\nThe malware grants outside entities full control of affected systems. All secrets, keys, and credentials stored on compromised machines must be rotated immediately from a different, unaffected computer.\n\nWhile the package should be removed, complete removal of all malicious artifacts cannot be guaranteed due to the level of system compromise. A full security audit and potential system rebuild may be necessary for affected users.
Indicators of compromise
- Packages
- @meli-testing/jest-react
Remediation
- Immediately remove the @meli-testing/jest-react package from all systems
- Rotate all secrets, keys, and credentials from a different, unaffected computer
- Conduct a full security audit of any system that had this package installed
- Consider rebuilding affected systems from clean media
- Monitor for signs of unauthorized access or data exfiltration
- Review logs for any suspicious activity during the period the package was installed
Sources
- GitHub Advisory GHSA-2rh8-4vrh-7vh3 · GitHub Advisory Database
Cite this entry
"Malware in @meli-testing/jest-react." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 31, 2026; last updated August 1, 2026. https://supplychainattack.org/incident/malware-in-meli-testing-jest-react-1o216s
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit