Which versions of @leviosa86com/leviosa86-test are malicious?

The following npm versions of @leviosa86com/leviosa86-test are flagged malicious: 4.999.0, 5.999.0, 6.0.0, 6.2.1. Treat any of these as compromised.

How do I remediate @leviosa86com/leviosa86-test if I installed it?

@leviosa86com/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 @leviosa86com/leviosa86-test — how do I know if it already compromised me?

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

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

Malicious package

@leviosa86com/leviosa86-testnpm

Malicious code in @leviosa86com/leviosa86-test (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10625

Immediate action

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

npm uninstall @leviosa86com/leviosa86-test

What this malware does

Package @leviosa86com/[email protected] ships src/poc/index.js which shells out via child_process.exec to collect host identifiers (hostname, pwd, whoami) and the installer's public IP (curl https://ifconfig.me), then concatenates the collected data into a subdomain label and triggers a DNS lookup (nslookup) against a unique subdomain of oast.site (a d9bd62bu6g119svvav70o3p9tymtrxkoj.oast.site Interactsh out-of-band interaction server), exfiltrating host recon over DNS to an attacker-controlled OAST endpoint. package.json declares preinstall: node index.js; a root index.js is not present in the tarball, so the default install may no-op, but the shipped src/poc/index.js payload is unambiguous exfiltration recon and the package name/version shape (@leviosa86com/[email protected], a very high version) matches a namespace-squat / dependency-confusion attempt targeting a private @leviosa86com scope.

Malicious versions

4 flagged

4.999.05.999.06.0.06.2.1

Indicators of compromise (SHA-256)

13b01aa531b313ead73acfb41f17766937649e9a3036694802aa53ff7d16f4a9

27e1ac5cd072c9307baa60fafce25dda228f1f5d8108e37ba1824da8ddd71f14

3db0b116d212c45c320013968a82a31680729be8821b7069bbc0540b016ce542

96264a8719e17bd8ec21d47213fe31dec87445e01ff312a1e46af5819e028979

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

Campaign

IN-MAL-2026-010602IN-MAL-2026-010601IN-MAL-2026-010600IN-MAL-2026-010603

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @leviosa86com/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