An attacker published poisoned patch releases of 16 @react-native-aria packages and one @gluestack-ui package on npm in June 2025.
The packages had more than one million weekly downloads combined. The injected code is a remote access trojan.
What happened
An attacker used a leaked npm access token from a maintainer. The token had no two-factor protection.
- The attacker published malicious versions of existing packages.
- The code sits on the last line of
lib/index.js, hidden by long runs of spaces. - The trojan connects to a command server and runs shell commands.
- It uploads files or whole directories.
- On Windows it adds a fake Python folder to the PATH variable to replace the python and pip commands.
The first package fell on 6 June 2025 at 21:33 GMT, and the poisoned releases stayed up for about 17 hours.
Affected versions
- In the @react-native-aria scope:
focus0.2.10,utils0.2.13,overlays0.3.16,interactions0.2.17,toggle0.2.12,switch0.2.5,checkbox0.2.11,radio0.2.14,button0.2.11,menu0.2.16,listbox0.2.10,tabs0.2.14,disclosure0.2.9,slider0.2.13,separator0.2.7. combobox0.2.8 per gluestack, 0.2.10 per BleepingComputer.- One @gluestack-ui package at 0.1.16 and 0.1.17. Gluestack names it @gluestack-ui/core. Aikido and BleepingComputer name it @gluestack-ui/utils. Treat both as suspect.
- Gluestack marked the bad versions as deprecated on npm. It did not unpublish them because other packages depend on them.
Indicators of compromise
- Command servers:
136.0.9.8and85.239.62.36, both on ports 3306 and 27017. - Windows persistence path:
%LOCALAPPDATA%\Programs\Python\Python3127. - Backdoor command names in the code:
ss_info,ss_ip,ss_upf,ss_upd,ss_fcd. - A lookup to
http://ip-api.com/jsonfor the public IP. - Very long space padding on the last line of
lib/index.jsin an affected package.
How to check
List every affected package in your dependency tree. Compare the versions with the list above.
npm ls --all | grep -E "@react-native-aria|@gluestack-ui"
Then search installed code for the indicators.
grep -rlE "136\.0\.9\.8|85\.239\.62\.36|ss_info" node_modules/@react-native-aria node_modules/@gluestack-ui
What to do now
- Find any affected version in your lockfile. Install a clean release from before the attack, delete node_modules and reinstall.
- If a bad version ran on a machine, treat the machine as untrusted. The sources say to rebuild it fully if the compromise is confirmed.
- Replace the secrets and tokens that were on that machine.
- Block the two command server IP addresses and review past traffic to them.
What Vigilance would show
These examples show an install hold and the corresponding owner report.
Example install message
Vigilance blocked `@react-native-aria/`. This version is too new or changed in a way Vigilance must check first.
Example owner report
Bad update
@react-native-aria/
User-interface components gained hidden code letting an outsider run commands on the developer's computer from far away.
No security team? See who reads the alert.
Frequently asked questions
Which gluestack and react-native-aria versions were compromised?
Sixteen @react-native-aria packages and one @gluestack-ui package. Two examples are @react-native-aria/focus 0.2.10 and utils 0.2.13.
How did the attacker get into the gluestack packages?
Gluestack says the attacker used a leaked npm access token that belonged to a maintainer. The token had no two-factor protection.
Sources
Send this page to the person who looks after AI at your company.