Which versions of ingka-test are malicious?

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

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

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

If ingka-test 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.

Is ingka-test part of a known attack campaign?

Yes — ingka-test is associated with the RLMA-2025-06364 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 ingka-test across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ingka-test (version 1.0.0).

Malicious package

ingka-testnpm

Advisory published Dec 23, 2025Updated Dec 24, 2025

ingka-test is a confirmed malicious npm package (MAL-2025-192802) 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 ingka-test (npm)

MAL-2025-192802

Immediate action

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

npm uninstall ingka-test

What this malware does

The package ingka-test was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

c287afcb61cd736f670406733155b3e35af3be992b8ac016a7283bf2a0fc940c

5e4ddc9c625f26973cfd60915965e422b52abe11d5fb35de173ebc5d01558cd3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06364

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ingka-test-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