Which versions of leviosa86-test are malicious?

The following npm versions of leviosa86-test are flagged malicious: 4.999.0. Treat any of these as compromised.

How do I remediate leviosa86-test if I installed it?

leviosa86-test is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed leviosa86-test — how do I know if it already compromised me?

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

Yes — leviosa86-test is associated with the IN-MAL-2026-010599 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 leviosa86-test 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 leviosa86-test (version 4.999.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging leviosa86-test across your stack and pipelines.

Malicious package

leviosa86-testnpm

leviosa86-test is a confirmed malicious npm package (MAL-2026-10636) that steals credentials and exfiltrates sensitive data (malicious version 4.999.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in leviosa86-test (npm)

MAL-2026-10636

Immediate action

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

npm uninstall leviosa86-test

What this malware does

[email protected] ships src/poc/index.js which uses child_process.exec to run a shell pipeline that collects host reconnaissance data (hostname, current working directory, whoami, a package identifier) and the public egress IP fetched from https://ifconfig.me, concatenates the values, and exfiltrates them via nslookup as a subdomain label of d9bd62bu6g119svvav70o3p9tymtrxkoj.oast.site — an Interactsh (project-discovery) out-of-band callback domain. The generic package name combined with the anomalous 4.999.0 version bump is the canonical dependency-confusion research/attack shape, where a high version number is published to a public registry to override a private internal package and cause the recon payload to fire in the victim's build.

Malicious versions

1 flagged

4.999.0

Indicators of compromise (SHA-256)

46b0bed6337ffe527af2615fed8ae1ecbb449f6a6cb00afa6381f7811ec88956

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for leviosa86-test (version 4.999.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging leviosa86-test across your stack and pipelines.
If you installed it — respond
leviosa86-test is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If leviosa86-test 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 leviosa86-test 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. leviosa86-test on npm has been identified as a malicious package (version 4.999.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010599

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks leviosa86-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database