Which versions of nflx-release are malicious?

The following npm versions of nflx-release are flagged malicious: 99.0.1. Treat any of these as compromised.

How do I remediate nflx-release if I installed it?

Remove nflx-release 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 nflx-release — how do I know if it already compromised me?

If nflx-release 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.

How do I find nflx-release across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nflx-release (version 99.0.1).

Malicious package

nflx-releasenpm

Advisory published Mar 19, 2026Updated Mar 23, 2026

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

Malicious code in nflx-release (npm)

MAL-2026-1580

Immediate action

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

npm uninstall nflx-release

What this malware does

The package nflx-release was found to contain malicious code.

The OpenSSF Package Analysis project identified 'nflx-release' @ 99.0.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.0.1

Indicators of compromise (SHA-256)

0e2efa2f26d254c047bb2b44e083fe717ce4d0a35d4b895358f3eccc4c6f4020

3868ddb111f719ba68b77cb727004735968c277712508099e138028047b7fd55

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for nflx-release (version 99.0.1).
If you installed it — respond
Remove nflx-release 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 nflx-release 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. nflx-release on npm has been identified as a malicious package (version 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks nflx-release-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