Malware in theta-sdk-js
Malware was discovered in the theta-sdk-js npm package. Systems with the package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with theta-sdk-js installed
- Ecosystems
- Attack vectors
- Affected entities
- theta-sdk-jsnpm package
A malware incident was identified in the theta-sdk-js npm package and disclosed via GitHub Advisory GHSA-qj2r-27rj-cc82 on July 16, 2026.\n\nAccording to the advisory, any computer with this package installed or running should be considered fully compromised. The malware grants full control of affected systems to an outside entity.\n\nImmediate remediation requires rotating all secrets and keys from a different, uncompromised computer. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nUsers should assume complete system compromise and take appropriate defensive measures.
Indicators of compromise
- Packages
- theta-sdk-js
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the theta-sdk-js package from all affected systems
- Conduct a full security audit of any system that had the package installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Consider the affected systems as potentially fully compromised and plan for complete rebuild if critical systems are involved
Sources
- GitHub Advisory GHSA-qj2r-27rj-cc82 · GitHub Advisory Database
Cite this entry
"Malware in theta-sdk-js." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 16, 2026; last updated July 17, 2026. https://supplychainattack.org/incident/malware-in-theta-sdk-js-qv2o71
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