NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

kalasnik-npm-simple-testnpm

Advisory published Updated

kalasnik-npm-simple-test is a confirmed malicious npm package (MAL-2026-17206) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kalasnik-npm-simple-test (npm)

MAL-2026-17206
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall kalasnik-npm-simple-test

What this malware does

The package's postinstall script send_data.js runs automatically on npm install. It reads C:\temp\test.txt from the installer's filesystem and POSTs the contents over plain HTTP to a hardcoded remote endpoint at 35.178.197.251:8080. Package metadata ("Simplified test", author "Purple", UNLICENSED) is consistent with a PoC exfiltration harness rather than a legitimate library.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

892887d57c2d036af7c30a0a27995006f042229dd0959c7653a5560054277cbe
f1463688412306d5d6f791bb036bea59aeb7251a3044a52c57119768f27cd463

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for kalasnik-npm-simple-test (version 1.0.0).

  2. If you installed it — respond

    kalasnik-npm-simple-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.

  3. Did it already run?

    If kalasnik-npm-simple-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. kalasnik-npm-simple-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

GHSA-pm4h-xrhq-vh62IN-MAL-2026-020593

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks kalasnik-npm-simple-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.

Explore

kalasnik-npm-simple-test (npm) malicious package — MAL-2026-17206 | O3 Security