Malicious code in @yane88/listary-02 (npm)
Description
The npm package @yane88/listary-02 versions 1.0.0 and 1.0.1 contains malicious code or depends on a malicious package. Installing or running this package can lead to full compromise of the affected computer, potentially exposing all stored secrets and keys. Immediate removal of the package and rotation of all secrets from a different, uncompromised machine is strongly advised. However, removal of the package may not fully eliminate the malicious presence due to potential persistent control established by the attacker.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The npm package @yane88/listary-02 in versions 1.0.0 and 1.0.1 has been identified as containing malicious code or relying on a malicious dependency. According to the source from amazon-inspector and the GitHub Security Advisory (GHSA-rg2v-g672-8773), any system with this package installed should be considered fully compromised. The advisory recommends immediate removal of the package and rotation of all secrets and keys from a separate, secure environment. The malicious code may have granted attackers persistent control, so simply uninstalling the package may not fully remediate the compromise.
Potential Impact
Systems with the affected versions of @yane88/listary-02 installed are at risk of full compromise. Attackers may have gained complete control over the system, potentially accessing or exfiltrating sensitive information such as secrets and keys. This level of compromise implies that trust in the affected system is lost, and all credentials stored on it should be considered compromised and rotated immediately.
Mitigation Recommendations
Remove the @yane88/listary-02 package immediately from all affected systems. Rotate all secrets, keys, and credentials that were stored or used on the compromised systems, performing this rotation from a different, trusted machine. Due to the possibility of persistent malicious control, further forensic investigation and system restoration from known good backups are recommended. There is no official patch or fix available for this malicious package; remediation relies on removal and credential rotation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-15659
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-rg2v-g672-8773"]
- Ecosystems
- ["npm"]
Threat ID: 6a9ad4e9acd9273b49b676ec
Added to database: 09/04/2026, 14:25:45 UTC
Last enriched: 09/07/2026, 17:39:57 UTC
Last updated: 10/04/2026, 09:37:19 UTC
Views: 21
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.