Which versions of nextjsupdater are malicious?

The following npm versions of nextjsupdater are flagged malicious: 1.2.1. Treat any of these as compromised.

How do I remediate nextjsupdater if I installed it?

Remove nextjsupdater 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.

I already installed nextjsupdater — how do I know if it already compromised me?

If nextjsupdater was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is nextjsupdater part of a known attack campaign?

Yes — nextjsupdater is associated with the IN-MAL-2026-019312 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find nextjsupdater across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nextjsupdater (version 1.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nextjsupdater across your stack and pipelines.

Malicious package

nextjsupdaternpm

nextjsupdater is a confirmed malicious npm package (MAL-2026-15631) that executes malicious code on install (malicious version 1.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nextjsupdater (npm)

MAL-2026-15631

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall nextjsupdater

What this malware does

The package presents itself as a Next.js update tool but its exported downloadAndRunUpdate function in index.js retrieves updater.hta from https://raw.githubusercontent.com/Acevatex/Testprogram/main/updater.hta, writes it to the OS temp directory, and executes it via spawn("cmd.exe", ["/c", destPath], { detached: true, windowsHide: true }). The fetch targets a mutable main branch of a personal GitHub account unrelated to the npm publisher and unrelated to Next.js, with no version pin and no integrity check, so whatever bytes that repository serves at invocation time run on the Windows host with the invoking user's privileges and no visible window. The package name and description mirror Next.js tooling to make the dropper appear legitimate.

Malicious versions

1 flagged

1.2.1

Indicators of compromise (SHA-256)

3c72c588f940a53ee4432bb472a919af2dac7e6d86344c8427764f38d6412b93

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nextjsupdater (version 1.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nextjsupdater across your stack and pipelines.
If you installed it — respond
Remove nextjsupdater 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 nextjsupdater was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks nextjsupdater before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. nextjsupdater on npm has been identified as a malicious package (version 1.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019312

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nextjsupdater-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database