Which versions of natateste are malicious?

The following npm versions of natateste are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate natateste if I installed it?

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

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

Yes — natateste is associated with the GHSA-29hr-9v6r-9qx7, RLMA-2026-01442 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 natateste 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 natateste (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging natateste across your stack and pipelines.

Malicious package

natatestenpm

Malicious code in natateste (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-395

Immediate action

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

npm uninstall natateste

What this malware does

The package natateste was found to contain malicious code.

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

1 flagged

1.1.0

Indicators of compromise (SHA-256)

b2bc57aed3208a3a97a2ed539e0782979641ab8312a75dcdb5056540c564d870

223884e033273ef49ab45ba4ac8c051419acbd5c7613c862e86fea2a817d5226

2e85bd3aa209c5b7cb92b65abdd45f9a93dd0c5b926f44e51f55f5d797f54b6e

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 natateste (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging natateste across your stack and pipelines.
If you installed it — respond
Remove natateste 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 natateste 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 natateste 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. natateste on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-29hr-9v6r-9qx7RLMA-2026-01442

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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