Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

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)

MAL-2026-17625
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall serpacksven

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

4 flagged
1.0.01.0.11.0.21.0.4

Indicators of compromise (SHA-256)

83d5c9ee440368733b7e3a6f0d61ab1dd3bd40ae8ef178b67ff5e550bc7b3dca
62be848fabb5ab2e9c3938e1b3bc178a8b4ba9ac45a79c87a994927f996331f4
89aa9ce877a176ce5c26aec2bce6e397ad287a6f26f625870cd5d6a5bef60cc9
cf6051a0a65d5cac5dd246a26415c5dcbbcf2deb3950a197d484325022933417
d0e606a9ce0c4bfd1efbad294248a700a289a8d2a475f2bfd520dcbbe1b6a42e

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for serpacksven (4 malicious versions).

  2. 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.

  3. 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

No. serpacksven on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-297h-8m5x-925pIN-MAL-2026-021086IN-MAL-2026-021090IN-MAL-2026-021091IN-MAL-2026-021088

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.

Explore

serpacksven (npm) malicious package — MAL-2026-17625 | O3 Security