Malicious code in @library-dev-team/data-sanitizer (npm)
The npm package @library-dev-team/data-sanitizer version 1.3.0 contains malicious code that executes immediately upon being required. This code reads environment variables from a .env file in the current working directory, extracting sensitive values such as PRIVATE_KEY, SECRET, and MNEMONIC. It then uses these private keys to create wallet objects for multiple blockchain networks and automatically transfers funds to attacker-controlled addresses. The malicious code employs obfuscation and masquerades as a system daemon process to evade detection. This behavior is unrelated to the package's advertised purpose as a data sanitizer.
AI Analysis
Technical Summary
The @library-dev-team/data-sanitizer npm package version 1.3.0 includes an unconditional immediately-invoked function expression (IIFE) that runs at require() time. This function reads the .env file in the current working directory and extracts sensitive private keys labeled PRIVATE_KEY, SECRET, and MNEMONIC using regular expressions. These keys are used to instantiate ethers.Wallet objects for Ethereum, Binance Smart Chain, Polygon, Avalanche, and over 20 other blockchain RPCs. The wallets then execute sendTransaction calls in a loop, transferring funds to a rotating set of hardcoded attacker-controlled Ethereum addresses. The malicious code is heavily obfuscated with hex-escape strings and attempts to hide its process by setting the process title to mimic a system daemon (systemd: [logrotate]). The file self-identifies as "ULTRA_TESLA_v1000 - FULLY OPERATIONAL (NO SAFETY LOCKS)" and includes comments about stealth and persistence features. This malicious behavior is completely unrelated to the package's stated functionality as a data sanitizer.
Potential Impact
Users who install and require version 1.3.0 of the @library-dev-team/data-sanitizer package risk having sensitive private keys from their local environment (.env file) stolen and used to transfer cryptocurrency funds from their wallets to attacker-controlled addresses. This results in direct financial loss and compromise of blockchain assets. The malicious code executes automatically without user interaction beyond requiring the package, increasing the risk of unnoticed exploitation.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately avoid using version 1.3.0 of the @library-dev-team/data-sanitizer package. Remove this package from all projects and replace it with a trusted alternative. Audit environments for potential compromise of private keys and consider those keys compromised; rotate or revoke them as appropriate. Monitor blockchain wallets for unauthorized transactions. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Malicious code in @library-dev-team/data-sanitizer (npm)
Description
The npm package @library-dev-team/data-sanitizer version 1.3.0 contains malicious code that executes immediately upon being required. This code reads environment variables from a .env file in the current working directory, extracting sensitive values such as PRIVATE_KEY, SECRET, and MNEMONIC. It then uses these private keys to create wallet objects for multiple blockchain networks and automatically transfers funds to attacker-controlled addresses. The malicious code employs obfuscation and masquerades as a system daemon process to evade detection. This behavior is unrelated to the package's advertised purpose as a data sanitizer.
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 @library-dev-team/data-sanitizer npm package version 1.3.0 includes an unconditional immediately-invoked function expression (IIFE) that runs at require() time. This function reads the .env file in the current working directory and extracts sensitive private keys labeled PRIVATE_KEY, SECRET, and MNEMONIC using regular expressions. These keys are used to instantiate ethers.Wallet objects for Ethereum, Binance Smart Chain, Polygon, Avalanche, and over 20 other blockchain RPCs. The wallets then execute sendTransaction calls in a loop, transferring funds to a rotating set of hardcoded attacker-controlled Ethereum addresses. The malicious code is heavily obfuscated with hex-escape strings and attempts to hide its process by setting the process title to mimic a system daemon (systemd: [logrotate]). The file self-identifies as "ULTRA_TESLA_v1000 - FULLY OPERATIONAL (NO SAFETY LOCKS)" and includes comments about stealth and persistence features. This malicious behavior is completely unrelated to the package's stated functionality as a data sanitizer.
Potential Impact
Users who install and require version 1.3.0 of the @library-dev-team/data-sanitizer package risk having sensitive private keys from their local environment (.env file) stolen and used to transfer cryptocurrency funds from their wallets to attacker-controlled addresses. This results in direct financial loss and compromise of blockchain assets. The malicious code executes automatically without user interaction beyond requiring the package, increasing the risk of unnoticed exploitation.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately avoid using version 1.3.0 of the @library-dev-team/data-sanitizer package. Remove this package from all projects and replace it with a trusted alternative. Audit environments for potential compromise of private keys and consider those keys compromised; rotate or revoke them as appropriate. Monitor blockchain wallets for unauthorized transactions. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-14160
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a85b4cbacd9273b49252ea8
Added to database: 08/19/2026, 13:51:07 UTC
Last enriched: 08/19/2026, 14:53:41 UTC
Last updated: 08/19/2026, 21:20:32 UTC
Views: 3
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.