Which versions of nc-verify-127942 are malicious?

The following npm versions of nc-verify-127942 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate nc-verify-127942 if I installed it?

nc-verify-127942 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed nc-verify-127942 — how do I know if it already compromised me?

If nc-verify-127942 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.

Is nc-verify-127942 part of a known attack campaign?

Yes — nc-verify-127942 is associated with the IN-MAL-2026-017668 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 nc-verify-127942 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nc-verify-127942 (version 1.0.0).

Malicious package

nc-verify-127942npm

Advisory published Aug 13, 2026Updated Aug 13, 2026

nc-verify-127942 is a confirmed malicious npm package (MAL-2026-13965) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nc-verify-127942 (npm)

MAL-2026-13965

Immediate action

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

npm uninstall nc-verify-127942

What this malware does

nc-verify-127942 declares a postinstall lifecycle hook ("postinstall": "node install-cb.js") that runs automatically on npm install. The install-cb.js script issues an HTTPS request and a DNS lookup to a Burp Collaborator subdomain under oastify.com (nc-verify-127942.owoemjgpf2c4qxqet92hexzvym4dsq6skvoa2cr.oastify.com), which confirms code execution on the installer's host and leaks install-side network identifiers (source IP, resolver) to an operator-controlled out-of-band endpoint. The package's own metadata labels it as a proof-of-concept for RCE verification; installing it in a normal developer or CI environment fires the beacon without any user interaction.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3ea69188e179cd73aa9f200d63e8faceb5d3aae622a8fe2d86bf7ae761b5f1e0

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for nc-verify-127942 (version 1.0.0).
If you installed it — respond
nc-verify-127942 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If nc-verify-127942 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. nc-verify-127942 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017668

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nc-verify-127942-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database