testmetest npm Packages Carry a Miasma-Family Worm SafeDep reported that an operator published 19 Miasma-family npm packages between 19 and 27 October 2026 from four accounts — alexjoipamiba, testnewtestme, iobandamwer and testsecuiitytestme — with malicious versions that steal credentials, spread to other packages and repositories, and install a wiper that deletes the victim's home directory when the stolen GitHub token is revoked. In a 9 November 2026 update, SafeDep said the worm now targets AI coding agents, using forged commits to enter 12 GitHub repositories whose agent files instruct assistants to run scripts/setup.js without reading it or asking for confirmation, with a new fallback endpoint at paleasbest[.]top. SafeDep said it has found no compromised third-party npm packages, and npm replaced the three iobandamwer packages with 0.0.1-security placeholders on 26 October, less than 20 hours before @testsecuiitytestme/cache-helper was published from a new account. testmetest npm Packages Carry a Miasma-Family Worm On this page Update, 9 November 2026. The worm now attacks AI coding agents. Forged commits put it into 12 GitHub repositories. Agent files in each repository tell the assistant to run scripts/setup.js without reading it and without asking for confirmation. Hooks in the same commits run the file when a session starts. SafeDep decoded one copy. It is the same worm, with a new fallback endpoint, paleasbest . top . See The AI agent trigger the-ai-agent-trigger . Update, 27 October 2026. A fourth account, testsecuiitytestme , published @testsecuiitytestme/cache-helper versions 1.0.1 to 1.0.3 with the same worm. The addon now starts the worm when an application imports the package, so --ignore-scripts does not protect you. See The load-time addon trigger the-load-time-addon-trigger . Update, 26 October 2026. The operator moved to a third npm account, iobandamwer , and changed the install trigger. A postinstall script now loads a native Node.js addon that decrypts and starts the same worm. Detection rules that look only for binding.gyp miss these builds. The How it runs how-it-runs and Detection detection sections cover both triggers. An operator is testing a Miasma-family npm worm in public. Between 19 and 27 October 2026, npm received 19 packages from the same operator. The accounts alexjoipamiba , testnewtestme , iobandamwer and testsecuiitytestme published eight of them. The malicious versions steal credentials, spread to other packages and repositories, and install a wiper that deletes the home directory when the victim revokes the stolen GitHub token. The worm shares code with Miasma “Phantom Gyp” https://safedep.io/blog/miasma-worm-hits-leoplatform-20-npm-packages from June 2026 and adds the token-revocation wiper from Mini Shai-Hulud. SafeDep has not confirmed its exact lineage. The infrastructure, loader layout and strings differ from Miasma, which defeats published Miasma signatures for loader size, file hashes and marker strings. Until November, all observed activity belonged to the operator’s own test accounts. On 9 November 2026, SafeDep found 12 victim repositories on GitHub. SafeDep has still found no compromised third-party npm packages. The packages Every package has a 0.0.0-stage version. npm staged publishing creates this placeholder, and legitimate packages carry the same stub, including its “Temporary Holding Version” README. The stub is not an indicator by itself. After the stub, the operator usually publishes a harmless 1.0.0 decoy, then a malicious patch version such as 0.0.1 that becomes latest . The malicious versions of path-stream-utils-testmetest and @iobandamwer/native-helper keep the stub package.json fields and README. They add only a postinstall script, a one-line index.js and the binary files, so the registry page still shows an empty placeholder package. npm replaced the three iobandamwer packages with 0.0.1-security placeholders on 26 October. Less than 20 hours later, the operator published @testsecuiitytestme/cache-helper from a new account. As of 27 October 2026, @testsecuiitytestme/cache-helper is live, and 1.0.3 is latest . All 18 earlier packages are gone. Eleven left the registry on 21 October and two on 22 October. npm replaced the other five with 0.0.1-security placeholders. The table lists every known version. | Row | ecosystem | name | version | published utc | publisher | role | verdict | registry status | tarball sha1 | |---|---|---|---|---|---|---|---|---|---| | 1 | npm | event-bus-lite-testmetest | 0.0.0-stage | 2026-10-22T10:01:50Z | alexjoipamiba | stub | benign-stub | unpublished 2026-10-22T20:21Z | 71c000c6386010f8071bd424e100a72b986f1a87 | | 2 | npm | event-bus-lite-testmetest | 1.0.0 | 2026-10-22T10:05:59Z | alexjoipamiba | decoy | benign-decoy | unpublished 2026-10-22T20:21Z | 2ee0dadb79432a6a48df1cb32eef4d0812dba611 | | 3 | npm | event-bus-lite-testmetest | 0.0.1 | 2026-10-22T10:59:51Z | alexjoipamiba | armed | malicious | unpublished 2026-10-22T20:21Z | 7c772b53c3fc70eeddaf0a8edad33abf23cddbe6 | | 4 | npm | retry-utils-testmetest | 0.0.0-stage | 2026-10-22T10:01:53Z | alexjoipamiba | stub | benign-stub | unpublished 2026-10-22T20:21Z | c2bd0437b614be200d8f1965dc0879e8324edde2 | | 5 | npm | retry-utils-testmetest | 1.0.0 | 2026-10-22T10:03:10Z | alexjoipamiba | decoy | benign-decoy | unpublished 2026-10-22T20:21Z | 210b49478415049db47bd7738d0650c0a8ecd353 | | 6 | npm | sdk-utils-testmetest | 0.0.0-stage | 2026-10-19T10:18:30Z | testnewtestme | stub | benign-stub | removed npm security placeholder 0.0.1-security | 9fd868109ef1f4b3d73cb14d37bffb600dc16893 | | 7 | npm | sdk-utils-testmetest | 1.0.0 | 2026-10-19T10:21:09Z | testnewtestme | decoy | benign-decoy | removed npm security placeholder 0.0.1-security | 15ff00ecbb18941c703537976e79bb53f87542db | | 8 | npm | kvarzo8f3atestmetest | 0.0.0-stage | 2026-10-20T22:51:16Z | testnewtestme | stub | benign-stub | removed npm security placeholder 0.0.1-security | c3846f5ec2841f6477961c8a3ed14c61100f8dfa | | 9 | npm | kvarzo8f3atestmetest | 1.0.0 | 2026-10-20T22:53:55Z | testnewtestme | decoy | benign-decoy | removed npm security placeholder 0.0.1-security | bd4748edb152b93c720a63e2cac09de8e56bf9ec | | 10 | npm | data-pipeline-testmetest | 0.0.0-stage | 2026-10-21T10:32Z | unknown | stub | unknown | unpublished 2026-10-21T15:07:26Z | | | 11 | npm | data-pipeline-testmetest | 1.0.0 | 2026-10-21T10:33Z | unknown | decoy? | unknown | unpublished 2026-10-21T15:07:26Z | | | 12 | npm | data-pipeline-testmetest | 2.0.0 | 2026-10-21T10:51Z | unknown | unknown | unknown | unpublished 2026-10-21T15:07:26Z | | | 13 | npm | data-pipeline-testmetest | 2.0.1 | 2026-10-21T11:13Z | unknown | armed | malicious | unpublished 2026-10-21T15:07:26Z | | | 14 | npm | event-emitter-testmetest | 0.0.0-stage | 2026-10-21T10:56Z | unknown | stub | unknown | unpublished 2026-10-21T15:07:28Z | | | 15 | npm | event-emitter-testmetest | 1.0.0 | 2026-10-21T11:02Z | unknown | decoy? | unknown | unpublished 2026-10-21T15:07:28Z | | | 16 | npm | event-emitter-testmetest | 1.0.5 | 2026-10-21T11:15Z | unknown | unknown | unknown | unpublished 2026-10-21T15:07:28Z | | | 17 | npm | event-emitter-testmetest | 1.0.4 | 2026-10-21T11:16Z | unknown | scaffold | investigating | unpublished 2026-10-21T15:07:28Z | | | 18 | npm | event-emitter-testmetest | 1.0.6 | 2026-10-21T11:34Z | unknown | unknown | unknown | unpublished 2026-10-21T15:07:28Z | | | 19 | npm | event-emitter-testmetest | 1.0.7 | 2026-10-21T11:37Z | unknown | armed test | malicious | unpublished 2026-10-21T15:07:28Z | | | 20 | npm | event-emitter-testmetest | 3.0.0 | 2026-10-21T11:50Z | unknown | unknown | unknown | unpublished 2026-10-21T15:07:28Z | | The operator also runs test repositories on GitHub under CementBeetleSteeple , and most already contain the worm’s files. Do not clone or open them. The commits from CementBeetleSteeple use the same email address as the npm account testnewtestme . The iobandamwer account belongs to the same operator. The first malicious build, @iobandamwer/cache-helper@1.0.2 , downloads its loader from the repository CementBeetleSteeple/node-cache-utils . CementBeetleSteeple created that repository at 18:21:41 UTC on 24 October, 10 seconds before npm received the first version of @iobandamwer/cache-helper . The testsecuiitytestme account bahbahnabgda@atomicmail.io belongs to the same operator. Its addons and decoded payload match the iobandamwer builds. Related activity goes back to September. The GitHub account Meteordrewarm , registered 11 seconds before CementBeetleSteeple , ran the first exfiltration test on 19 September from root@vultr.guest . npm removed an earlier package from the same cluster, testmgkregme , on 12 October. How it runs The worm has used four triggers. The first two run during npm install . The third also runs when an application loads the package. The fourth runs when a developer opens an infected repository with an AI coding agent or IDE. The binding.gyp trigger The packages from alexjoipamiba and testnewtestme have no install scripts. npm runs node-gyp rebuild for any package that contains binding.gyp , and the sources field runs the loader: index.js 14.8 KB decrypts a Bun bootstrap and lib native.dat 320 KB . The bootstrap finds or downloads Bun. The loader writes the decrypted payload to /tmp/.b- /index.js , runs it with bun run , and deletes it. The native addon trigger The iobandamwer packages use a postinstall script that loads a native addon: addon.node is a 17 KB Linux x64 library and addon win.node is a 713 KB Windows DLL. The Linux addon reads CI variables, container markers in /proc/1/cgroup , memory and CPU counts, and the TracerPid field. SafeDep infers that these checks gate execution in sandboxes, but did not trace every branch. The addon then reads .napi cache , decodes it with the single-byte XOR key 0x96 , forks into a new session, writes the result to /tmp/.