Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@bigtest/agent
Advanced tools
Agent for connecting test environments (browsers) to BigTest
Bigtest agents are applications that run in process with the system under test that accept commands on behalf of, and report results back to, the bigtest server.
This package contains an agent for web browsers, and also a web application to serve it to browsers.
To start an agent server in process, you can use the
AgentServer.create()
operation, passing it the websocket url where
the bigtest server will be accepting connections from agents.
import { main } from 'effection';
import { AgentServer } from '@bigtest/agent';
main(function* run() {
let agentServer: AgentServer = yield AgentServer.create('ws://localhost:5000');
console.log('connect browsers to ${agent.agentAppURL}');
});
By default, the agent will connect to a random available port and
serve the agent app from agent.agentAppURL
;
The AgentServer class serves the web agent which is the agent that
adapts browsers to bigtest, but you can write your own agents that can
adapt any runtime that supports websockets to be a testbed for
BigTest. You can do this with the Agent
class.
import { main } from '@effection';
import { Agent, Command } from '@bigtest/agent';
main(funtion*() {
let socket = WebSocket('http://localhost:1234');
let agent = yield Agent.start(socket);
// let the orchestrator know that you're here!
agent.send({
type: 'connected',
data: 'secret agent'
});
// await for commands from the orchestrator
while (true) {
let command: Command = yield agent.receive();
// the orchestrator wants us to do something. let's do it!
yield handleCommand(command);
}
});
Normally, the server will start an agent for you, but in order to
develop the agent code, you'll want to start a development agent at a
given port, and then point your bigtest server at it at the known
location. To do this, run the start
command. This will start a
parcel server to continually watch and build the application as you
develop. Any arguments will be passed on to parcel.
$ yarn start --port 5000
Server running at http://localhost:5000
✨ Built in 463ms.
You can now, in your server code, instantiate the AgentServer with the
AgentServer.external()
method:
let server: AgentServer = yield AgentServer.external('http://localhost:5500', 'ws://localhost:5000');
console.log('connect browsers to ${agent.agentAppURL}');
Now, the agent url will connect to the development agent.
To run the tests:
$ yarn test
The tests use a faked manifest, which is editable in
test/fixtures/manifest.src.js
. If you make any changes to this file, you
must rebuild the compiled manifest like this:
$ yarn manifest:build
FAQs
Agent for connecting test environments (browsers) to BigTest
The npm package @bigtest/agent receives a total of 146 weekly downloads. As such, @bigtest/agent popularity was classified as not popular.
We found that @bigtest/agent demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.