Use of software with malware In serpacksven2
Description
The tarball ships ten identical files with misleading extensions (1.png, client.doc, json.txt, server.doc, for.you.doc,.txt,.txt.1,.txt.2, and an extensionless 'client'), all sharing the same SHA-256 and all containing the same PowerShell script. The script hides its console window and moves it off-screen via SetWindowPos, concatenates roughly 150 base64 chunks, XOR-decodes them, and passes the resulting bytes to System.Reflection.Assembly.Load().Invoke — an in-memory.NET assembly loader characteristic of RAT/stealer stagers. The package has no index.js, no main entry, and no lifecycle scripts, so npm install and require() do not themselves run the loader; the package exists purely to deliver and disguise the staged PowerShell/.NET payload for later execution on the host.
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.
Mitigation
Update Impact
Minimal update. May introduce new vulnerabilities or breaking changes.
Ecosystem | Component | Affected version |
|---|---|---|
npm |
Aliases