Which versions of technical-assignment are malicious?

The following npm versions of technical-assignment are flagged malicious: 1.1.0, 1.1.1. Treat any of these as compromised.

How do I remediate technical-assignment if I installed it?

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

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

Yes — technical-assignment is associated with the RLMA-2026-01610 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 technical-assignment across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for technical-assignment (2 malicious versions).

Malicious package

technical-assignmentnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

technical-assignment is a confirmed malicious npm package (MAL-2026-1861) that executes malicious code on install (malicious versions 1.1.0, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in technical-assignment (npm)

MAL-2026-1861

Immediate action

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

npm uninstall technical-assignment

What this malware does

The package technical-assignment was found to contain malicious code.

Malicious versions

2 flagged

1.1.01.1.1

Indicators of compromise (SHA-256)

d99e7f3a47bafbbbfe2014e6da15707b7b02cb6543ac1a86ad4775e41a8c7701

7bb4466031b35e68c6b2433674215383e95538391f583e01c1800c758a61c53b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for technical-assignment (2 malicious versions).
If you installed it — respond
Remove technical-assignment 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 technical-assignment 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. technical-assignment on npm has been identified as a malicious package (versions 1.1.0, 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01610

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks technical-assignment-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