Which versions of testtestkjkldfnjdfn are malicious?

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

How do I remediate testtestkjkldfnjdfn if I installed it?

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

If testtestkjkldfnjdfn 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 testtestkjkldfnjdfn across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for testtestkjkldfnjdfn (version 1.0.0).

Malicious package

testtestkjkldfnjdfnnpm

Advisory published Oct 26, 2026Updated Nov 5, 2026

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

Malicious code in testtestkjkldfnjdfn (npm)

MAL-2026-18697

Immediate action

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

npm uninstall testtestkjkldfnjdfn

What this malware does

testtestkjkldfnjdfn ships nebula.js, byte-identical to the nebulajs-api payload, and a preinstall.cjs that is a single opaque Function(...) call decoding XOR-encrypted code at install time. It is a new name for the nebulajs-api (MAL-2026-17220) campaign; the file hashes below match that record's evidence. The package presents itself as an ordinary utility, so the code runs on import or install without the user knowing.

Malicious versions

1 flagged

1.0.0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for testtestkjkldfnjdfn (version 1.0.0).
If you installed it — respond
Remove testtestkjkldfnjdfn 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 testtestkjkldfnjdfn 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. testtestkjkldfnjdfn 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.

References

Credits

CyberXYZ · finder

Detect & block this

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