serpacksvennpm
Advisory published Updated
serpacksven is a confirmed malicious npm package (MAL-2026-17625) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in serpacksven (npm)
What this malware does
The tarball contains only package.json and json.txt. The declared main (index.js) is absent, so requiring the package fails — the package is not a functional JS library. json.txt is a heavily obfuscated PowerShell script that hides the console window via GetConsoleWindow + ShowWindow(0) and SetWindowPos to offscreen coordinates (-32000,-32000), performs randomized sleeps and junk-variable noise, concatenates ~150 base64 string fragments into one buffer, base64-decodes and XOR-decrypts it with key 89, then reflectively loads the decoded bytes as a.NET assembly through a runtime-constructed [System.Reflection.Assembly]::Load invocation whose type and method names are rebuilt from char-code arithmetic. The in-memory.NET payload is opaque and attacker-controlled. The package has no lifecycle scripts, so installation alone does not execute json.txt, but any environment that invokes the shipped file via powershell will run the embedded payload. The disguised.txt extension, cover-story main entry, console-hiding, anti-analysis obfuscation, and reflective load of an opaque buffer are the signature of a malware staging artifact rather than legitimate tooling.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for serpacksven (4 malicious versions).
If you installed it — respond
Remove serpacksven from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If serpacksven was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks serpacksven-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.