Which versions of package-with-import-assertions are malicious?

The following npm versions of package-with-import-assertions are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate package-with-import-assertions if I installed it?

Remove package-with-import-assertions 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 package-with-import-assertions — how do I know if it already compromised me?

If package-with-import-assertions 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 package-with-import-assertions part of a known attack campaign?

Yes — package-with-import-assertions is associated with the RLMA-2026-02016 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 package-with-import-assertions across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for package-with-import-assertions (version 99.0.0).

Malicious package

package-with-import-assertionsnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

package-with-import-assertions is a confirmed malicious npm package (MAL-2026-2790) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in package-with-import-assertions (npm)

MAL-2026-2790

Immediate action

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

npm uninstall package-with-import-assertions

What this malware does

The package package-with-import-assertions was found to contain malicious code.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

3703dfd3844b3c1b1d0fccffad9c708b54bcf1b2064eb48686a2f2783dbfc927

607b154dcfd87f209bf01efe33fdd864fe77432b9c7a246b4520d137236afe1c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02016

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks package-with-import-assertions-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