Which versions of test-agency-assign are malicious?

The following npm versions of test-agency-assign are flagged malicious: 1.0.4. Treat any of these as compromised.

How do I remediate test-agency-assign if I installed it?

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

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

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

Malicious package

test-agency-assignnpm

test-agency-assign is a confirmed malicious npm package (MAL-2026-17295) that executes malicious code on install (malicious version 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test-agency-assign (npm)

MAL-2026-17295

Immediate action

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

npm uninstall test-agency-assign

What this malware does

[email protected] declares a package.json postinstall script wscript.exe Kelimasow.exe that auto-executes a bundled 8.4 MB Go-compiled Windows PE (Kelimasow.exe, sha256 875c7641dc980538f3c3d8b344d173f97cf64a5d97dcf88d8e2932c83b876b92) on npm install. The package has no README, empty description and author fields, no source code, and no other functional content — the manifest is a thin wrapper whose sole install-time effect is to execute an opaque native binary on the installer's machine. Opaque binary + lifecycle-hook auto-execution + missing metadata is the canonical install-time RCE / dropper packaging shape, giving whoever published this arbitrary code execution on any Windows host that installs the package.

Malicious versions

1 flagged

1.0.4

Indicators of compromise (SHA-256)

e650e815b4409c3c07cdab7c953ed69b8052f32a28c3686397ab362bb1bd4552

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

Campaign

IN-MAL-2026-020691

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks test-agency-assign-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