Which versions of mnteckets are malicious?

The following npm versions of mnteckets are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate mnteckets if I installed it?

mnteckets is a typosquat — you almost certainly intended a legitimately-named package. Remove mnteckets, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

If mnteckets 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 mnteckets part of a known attack campaign?

Yes — mnteckets is associated with the GHSA-ghqw-mfq6-xh36, IN-MAL-2026-017470, IN-MAL-2026-017468 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 mnteckets 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 mnteckets (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mnteckets across your stack and pipelines.

Malicious package

mntecketsnpm

mnteckets is a confirmed malicious npm package (MAL-2026-13824) that typosquats a legitimate package to trick installs (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mnteckets (npm)

MAL-2026-13824

Immediate action

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

npm uninstall mnteckets

What this malware does

The tarball contains only package.json and index.html. package.json declares no lifecycle scripts (preinstall/install/postinstall/prepare) and sets main to index.html, which Node cannot execute via require()/import. index.html mimics a Cloudflare Turnstile challenge and, on the challenge callback, builds a redirect URL via obfuscated string concatenation (new URL('https://mi'+...)) and calls window.location.assign to navigate the browser away. The redirect only fires when a user opens the HTML file in a browser; installing or requiring the package from Node performs no code execution and reads no installer data. The package appears to be registry-hosted phishing/redirect content rather than a supply-chain attack against npm installers.

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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

766e56cadc18b6635f490afe840cff6f39b4f1073c098613d8a3b28e0ccd766d

50d8627ece49121a7dbc9c5a0dd2da75874428d23878df4c21677663debbe9ba

caa458e1b7c6ca828e971aa0dac44b11b2f20aaf55652235ce2a4c5ce1c4fd66

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mnteckets (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mnteckets across your stack and pipelines.
If you installed it — respond
mnteckets is a typosquat — you almost certainly intended a legitimately-named package. Remove mnteckets, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If mnteckets 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 mnteckets 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. mnteckets on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-ghqw-mfq6-xh36IN-MAL-2026-017470IN-MAL-2026-017468

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mnteckets-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